Select to view content in your preferred language

Utility Network tolerance value

811
2
Jump to solution
10-19-2023 02:55 AM
OliviaGill3
Occasional Contributor

How are tolerances set in the Utility Network and is there a default value. And if possible how can these be amended?

Any info is appreciated.

0 Kudos
1 Solution

Accepted Solutions
RobertKrisher
Esri Regular Contributor

While @AyanPalit is correct about being able to change the XY tolerance and resolution I would caution you against changing these values because they are permanent, and they can have unexpected consequences.

If you're having issues with features not being connected in your network because of the resolution/tolerance of your source database, then the recommended approach is to include a process to snap and correct these features during your migration to the utility network (using FME or geoprocessing tools). This gives you an opportunity to experiment with different snapping tolerances so you can find the right tolerance that minimizes topology errors and manual cleanup, while also maximizes the number of features that are connected (appropriately).

View solution in original post

2 Replies
AyanPalit
Esri Regular Contributor

@OliviaGill3 Tolerance and Resolution for XY, Z and M are set based on the spatial reference at the  asset package schema of Utility Network. These settings are preserved when configuring the Utility Network by 

The XYZM tolerance and resolution may be modified using the Change Asset Package Spatial Reference tool that is part of the Utility Network Package Tools to automate the process of creating and configuring a utility network using asset packages for specific industry domains.

Reference:

Utility network creation and configuration

Utility Data Management Support tools - 2.9.3/3.1.1 Release

Ayan Palit | Principal Consultant Esri
RobertKrisher
Esri Regular Contributor

While @AyanPalit is correct about being able to change the XY tolerance and resolution I would caution you against changing these values because they are permanent, and they can have unexpected consequences.

If you're having issues with features not being connected in your network because of the resolution/tolerance of your source database, then the recommended approach is to include a process to snap and correct these features during your migration to the utility network (using FME or geoprocessing tools). This gives you an opportunity to experiment with different snapping tolerances so you can find the right tolerance that minimizes topology errors and manual cleanup, while also maximizes the number of features that are connected (appropriately).