Utility Network Migration Toolset Workflow for Electric - Part 2 of 2
Introduction
Happy Holidays Esri Community! My name is Jess Gooch, and I am a Senior Solution Engineer at Esri. In this blog I will walk you through some new tools that were released this year that help infrastructure customers with their migration from the Geometric Network to the Utility Network by assessing data readiness and how to fix topology errors in preparation for migration. This is part 2 of a blog series and webinar that was released earlier this year.
In 2025, Esri released a new toolbox and geoprocessing tools called the Utility Network Migration Toolset for ArcGIS. The Migration toolset is designed to migrate geometric network data stored in a geodatabase to the new utility network dataset. My coworkers and I have been using the tools and talking to customers about them. We’d like to share what we’ve learned migrating an Electric Dataset into the electric utility network.
Through this blog series, we’ll go through the steps to migrate the data, run the Analyze Network Data tool to identify the types of electric data errors that will impact network connectivity and then deciding on the best approach to resolve those errors.
In part one of this blog series, we walked through how you can use the new Utility Network Migration Wizard to migrate your data to a utility network.
Once the wizard has been run, the results are a geodatabase that contains a . The next step that he walked us through was how to analyze the network data to identify errors in the data that will need to be resolved before moving forward to enabling topology.
In this next step in the series, we will show you how to resolve common errors in your newly migrated data.
Pre-Requisites
- ArcGIS Pro 3.5.2*
- A mobile geodatabase containing your migrated data and analyzed network results.
*Currently these tools are supported in ArcGIS Pro 3.5.2
Analyze your Network Data and Resolve Errors
In the first blog we migrated and analyzed our data. we can begin to walk through the process of resolving our errors. We can enable topology when errors exist, but error objects will negatively impact your trace analysis. You SHOULDN’T enable topology until all errors are resolved.
For a complete run down of Analyzing and resolving topology errors, check out this blog by Robert Krisher.
Resolve Network Errors – Reviewing the Results
In the previous article, we ran the Analyze Network Data tool, and the result was a geodatabase of all the errors that need to be resolved, two charts that show us the errors in bar graphs and an error resolutions table.
It is recommended that you drive the workflow from the Error Summary table. This allows the user to see how many rows there are in the table and how many sets of resolutions you will need to provide.
In this sample dataset we have the following errors to be resolved:
- Stacked points
- Missing junction (end-end)
- Vertex withing tolerance
- Duplicate vertices
- Self-intersecting lines
- Empty geometry
Each error type can be resolved by setting an Action in the Errors Resolution table.
As we review each error type, we can decide which Resolution Action to take.
Resolving errors in the new geodatabase will not fix the errors in your source data (geometric network).
Let’s review how we will resolve each error.
Stacked Points
This error occurs when two or more junctions or devices are in the same location. This could be stacked electric service meters, or in this case we have default network junctions from our geometric network that are stacked with our risers.
The most common resolution to this error is to use the “Delete all but first” choice. You would find the feature you want to keep and set its action to Delete all but first. If there are multiple asset types that are stacked, you need to apply this to one of them and delete all to the rest of them.
Missing Junction End to End
This error is caused when two or more different types of lines are being drawn in a way that they could be connected but there is no device or junction that allows them to be connected. The most common resolution is to create a junction that allows the features to be connected.
In this case, we have chosen to Create an Electric Junction – Miscellaneous Feature – Riser to resolve the error.
Vertex within Tolerance
While technically not a topology error, if these snapping issues are not resolved they can result in features becoming disconnected or de-energized in the network. To solve these issues, you will set one feature to act as an anchor, and the other nearby features to snap.
Duplicate Vertices
Duplicate vertices occur when a line has two or more duplicate vertices with the xy and at the same z value. The most common way to fix these errors is to delete the duplicate vertices.
Self-intersecting line
This occurs when the geometry of a line intersects itself. The error location feature will indicate the specific vertex where the line intersects itself and the group key column on the error summary will indicate if there are other features present at that location.
It is important to take note of how many different types are listed in the records in error column, because this will determine how you apply resolutions to the fix.
The most common resolution to this error is to delete the vertices responsible for the line intersecting itself. If there is only a single type in the records in error column, find the line for the error in the resolutions table, and set its action to Delete all but first.
Empty Geometry
This error occurs when a line feature has an empty geometry. The only automated resolution to this error is to delete the feature, since an empty geometry cannot be updated. The most common resolution to this error is to manually draw the geometry of the feature, if you can identify its location. If you wish to automatically delete this feature through an action in the error resolution tool, find the row in the Error Resolution table with this error code and set its action to Delete all.
We have now set all the error resolutions and are ready to run the next tool in the series.
Running the Error Resolutions Tool
Once you have selected all the resolutions for each error type you will run the Apply Error Resolutions tool in the Utility Network Tools > Migration toolbox
Fill out the parameters and click Run
To note: the Output Location and Output Name are optional. If you do populate these parameters, they will generate an error log.
This is an iterative process and there may be times when you will need to run the tools multiple times. The goal is to get to a clean database with no errors.
Migrated and Clean Database
The network data has now been migrated and cleaned and we are now ready to enable the topology and begin to use our new utility network.
We can now enable topology.
Now that the topology has been enabled, we can run a connected trace on our network.
Conclusion
In this blog post we showed you how to analyze your migrated data, how to correct common errors and then we enabled network topology to show the connected network.
Migrating your data is just the first step in the process. You still need to work through any data quality issues, adjust the model to suit any business requirements you have, and begin testing your organization’s workflows using the new model. You can find examples and resources supporting these activities on the Esri Community site.
