Hey All,
Had a question pertaining to proposed assets in a Water Distribution UN. I am working with a client that currently digitizes proposed water mains and services as "pulled-back" from active mains. In some cases, their configuration has created topology errors due to gaps in feature connectivity or junctions missing.
I wanted to see what the community's experience has been with this, as to how to manage these transient asset states during a migration, to minimize the amount of cleanup required post-migration. I had theorized that perhaps a snapping operation could be ran during the migration on any proposed features (e.g, prior to loading data into the asset package and converting to a UN) but wanted to see if there is a better method to tackle this. We are excluding abandoned assets in this migration, as there are far too many and the only alternative we had found was faking z-values to remedy most of the stacked point issues.
Thanks for any input!
