Introduction

In the years since we’ve released the ArcGIS Utility Network we’ve discovered that a handful of different topology errors account for the majority of errors that our users experience on a daily basis. We’ve greatly expanded our online documentation on this topic to include all of the errors along with the approaches for resolving them.  However, because these errors and their resolutions are specific to different industries we’ve decided to develop this blog that provides examples and screenshots for all of these major issues and their corresponding solutions.

By reading this article you will be better equipped to understand how to interpret these errors and what techniques you can apply to the decision-making process for resolving them.  We continue to improve the error management and quality assurance experience and hope that this series of content will go a long way to improving your daily experience.

There are a disclaimers with the content you will find in these articles:

• Resolutions that require adding or removing rules will require users to disconnect from the system while the admin disables and enabled the topology to make the change.  Changing your rules can also introduce new errors if existing features were relying on those rules, so it’s recommended you test out these changes in a staging environment or file geodatabase first.
• The examples provided in this and other articles made use of the latest data models and software at the time of publication.  There may be slight changes made to user interfaces or data models over time.
• The errors and proposed solutions were all manufactured for demonstration purposes only and resolutions for the same error will vary due to differences in business requirements, data model, and drawing standards at every utility.
• The validation framework is only able to validate features that have valid geometries and are connected.  If your data is not well snapped or has invalid geometries the framework will not be able to perform additional validation.

Industry Specific Examples

Check out one of the following blog posts for industry specific examples of how to identify and resolve errors.

• Electric
• Gas and Pipeline
• Water

Cheat Sheet

Below you can find a table that can be used as a quick reference for the most common types of topology errors customers encounter with their data.  You can download a printer-friendly version of this table from the Utility Network Community on the Esri Community page.  Feel free to save a copy of it and refer back to it often!

Viewing Rules

Some of the errors require that you know what network rules are configured in your database and there are several ways you can do this.  For instructions on how to review all the rules in a network read the view network rules page in the online help for instructions on how to do this.

There is also a  toolbox provided by ArcGIS Solutions that allows you to see all the rules configured for a given feature, which is convenient for troubleshooting purposes.  You can access this tool and learn more about some of the other tools provided by the ArcGIS Solutions team by reading the Utility Data Management Support blog.  I have provided an abbreviated version of the instructions for using the “Configure UN Layers” tool here, for reference purposes.

Once you have downloaded the tools and added the toolbox to your project, open the “Configure UN Layers tool”

Check the box next to “Rule Popup”.  By default the tool will only modify your active map in your current project, on your active map so you can leave these parameters alone if this is what you want.  It is recommended you pause your map before running this tool, since the map will refresh every time a layer is updated.

Once the tool finishes running you will find the list of rules for a feature at the bottom of your popup.  Feel free to modify its location or style using the configure pop-up tool.

Additional Resources

1. For a full list of all the possible network errors, refer to the Error Management page in the online help.
2. For a detailed explanation of all these errors and their resolutions, refer to the Fantastic errors and how to fix them: part 1 blog post.