Latest Contributions by RobertKrisher

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. ... View more

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

@MikeMillerGIS  ... View more

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. ... View more

@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. ... View more

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

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. ... View more

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. ... View more

@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.   ... View more

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

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. ... View more

@PierreloupDucroix I was not suggesting using the add index tool to create your own unique index on this field. I was showing how the OOTB field should look once the enterprise data is versioned. I recommend you log a case with support about the append tool not working on branch versioned data. ... View more

Also, instead of using Asset Group codes or Asset Type codes for your filters, consider using a network category. Asset groups/type codes are not guaranteed to be unique, and using a network category allows you to exclude/include multiple asset groups/types with a single category. It also makes the filter easier to understand. Saying you're excluding asset group 12 doesn't mean much, but saying you're excluding something like "cathodic equipment" or "high voltage" does. ... View more