Latest Contributions by RobertKrisher

‎04-06-2026

Disregard what @VenkataKondepati said about there being a utility network in the configuration tab. That is not a thing. I think he meant to tell you to enable the version management option (which you do have enabled). In your statement you said you're going to ArcGIS Online, but I assume you meant to say ArcGIS Enterprise? You will add the data to your map using a feature service (this is discussed in the online help linked to above and the article I posted). All of the items on the ribbon should be come enabled when a) there is a utility network in the map and b) you have the appropriate licenses applied to your named user.

‎04-06-2026

Make sure the map you used to publish your feature service has the utility network in it, and you should review the list of missing tables and consider including those in your service as well. The steps are outlined in this article: Deploying a utility network to ArcGIS Enterprise If you end up dropping/re-adding any layers make sure that edit the properties of each layer so the layer IDs on your updated service match your original serviec.

‎04-02-2026

Vertex within tolerance will not generate topology errors, but they are data quality issues that can result in problems with tracing and editing. In terms of applying resolutions not fixing all the errors, that shouldn't be the case, but I can imagine there are some edge cases that the tool may not be able to handle. If there are a relatively small number of them than you may be better off manually resolving them. By doing that you will probably understand why the automated tool is not able to correct them. If you plan on running subsequent migrations, you should also look at correcting the problems in your source database.

‎04-02-2026

@BrettJohnston1 while Tom finds and updates the link, I think it might be the one listed with the foundation here: UPDM_dynamic

‎04-02-2026

@MikeMillerGIS

‎03-31-2026

To add onto what @gis_KIWI4 said, you don't want to just pass everything into an anchored snapper. That would be a mess. What you want to do is use transformers to identify the problem, and apply a targeted fix precisely. Mature data migration vendors have already worked out the logic for doing this reliably and safely. When done improperly, this can lead to topology errors (self-intersecting lines, duplicate vertices, etc) and disconnected features (stacked points, missing vertices, etc). But if you don't have too many of these you and/or you have enough free time and grit then it is a tractable issue.

‎03-31-2026

@Jeremy_Hayden If the data is registered as versioned and you unregister it as versioned, then you will lose all your history. Non-versioned archiving uses a separate mechanism and should not be confused with the Archiving used by Branch Versioning. I don't deal with non-versioned archiving regularly enough for me to want to commit to the specifics of its behavior on a public forum, but since this is outside the scope of your question I'll leave it alone for now.

‎03-30-2026

Analyze network data does not consider your edge-junction-edge rules so it will report errors for anything that would be resolved by an edge-junction-edge rule. If you are confident there is a rule that satisfies the problem, then you can ignore what is reported by Analyze Network Data.

‎03-30-2026

Analyze Network Data does not consider edge-junction-edge rules. Apply Error Resolutions only considers and can add Junction-Edge rules.

‎03-30-2026

Building live SQL views directly on the branch versioned data is not recommended, but if you had a read-only instance where you materialized the contents of the views that would be a more performant approach. Doing this requires a strong understanding of the branch versioning model as well as a strong understanding of how associations are represented in domain networks AND telecom domain networks. It would be very difficult to write a SQL view that could do all that in an efficient manner, on the fly.

‎03-27-2026

I'm not aware of any single tool that will automatically fix all these issues in a way that creates a usable topology. FME / Data Interop have many powerful tools for finding these situations and performing geometry manipulation to resolve them, there are also core Python and GeoProcessing tools you can use to identify them. If you have a lot of these issues, or other, issues to fix you should consider reaching out to a distributor or business partner with data migration experience. Many of them have already developed models to identify and resolve these issues.

‎03-27-2026

You need to connect to a machine that has a better (i.e. lower latency) connection to your SDE environment. Even if you use something like an asset package to redeploy the database, you're going to run into the same problem with latency. If you don't have a good, local connection to your SDE you should have a machine co-located with your SDE infrastructure that has ArcGIS Pro installed for administrative purposes. Some customers choose to have a dedicated machine, others will install ArcGIS Pro on one of the machines in their ArcGIS Enterprise deployment.

‎03-26-2026

@PierreloupDucroix index issue aside ... I had some issues getting the Append to work properly, until I read the doc more closely and realized that the Preserve Global ID option will only be respected on append (at the REST level) when defining a Matching Field, which places the tool in an Upsert Mode.

‎03-25-2026

Yes, curves are supported by the utility network and ArcGIS Pro.

‎03-25-2026

If you create a utility network and register it as versioned you should get a unique index. You should then be able to run the append tool, with the preserve global id option, against a branch versioned service into a named version. I'm not sure what the add tool is, or whether you meant the append tool.

Online Status	Online
Date Last Visited	yesterday

My Ideas

Latest Contributions by RobertKrisher

Re: Gas Utility Network Publishes as Feature Layer not Utility Network

Re: Gas Utility Network Publishes as Feature Layer not Utility Network

Re: Duplicate Vertices in UN but not in Check Geometry

Re: Utility and Pipeline Data Model 2026 is Released

Re: Batch Trace Script: ExecuteError: 'in-table' is not table or a featureclass

Re: Undershoot/Overshoot Geometric Error Fixes

Re: Does historical data persist when unregistering and then re-registering a feature class?

Re: Rule Missing Error - but rule exists in Network Properties

Re: Rule Missing Error - but rule exists in Network Properties

Re: Best practices for managing and validating Utility Network associations in telecom (FTTH) after migration to SDE

Re: Undershoot/Overshoot Geometric Error Fixes

Re: Migrating a UN that exists in a Mobile GDB to SDE

Re: Creating a Utility Network creates a non unique index on globalid

Re: Curves in the Utility Network

Re: Creating a Utility Network creates a non unique index on globalid

Re: Feedback on the Prune Branch History Tool

Re: Utility Network Sewer Main Lines: Labeling Iss...

Re: Change Asset Package Spatial Reference Deletes...

Re: Supported workflow to add new fields to existi...

Re: Change Asset Package Spatial Reference Deletes...

European Utility Network Community (UNC)

APAC Utilities Community of Practice