nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

UN Migration Toolset not honoring Asset Type field input

NathanGEOregon

Working on our Water UN Prototype, and have successfully delineated all of our primary pressure zones. That felt like a big milestone! I’ve now gone back to the drawing board (re-running Migrate to Utility Network) to try to assign Asset Types to our Water Valves so that I can set Pressure Reducing Valves as subnetwork controllers for delineating our closed PRV subnetworks.

The tool seems to run fine using our “Valve Function” field as the Asset Type input. But after the tool completes, all water valves still have “Water_Valve” as the Asset Group and Asset Type. It’s not splicing or dicing the Asset Type based on the Valve Function field as I expected.

Edit: I do see that it is possible to add Asset Types without needing to "start over" but I kind of want to see how the process goes rebuilding the UN from scratch with the cleanup that I completed thus far.

Any thoughts or recommendations are appreciated!

Trouver plus de publications taguées avec

Accepted answers

NathanGEOregon

It worked after I mapped the string data over to a new Integer field and created an Integer coded domain and re-ran the Migrate to Utility Network tool.

(I did download the Utility Network Tools 3.3.3 as Mike recommended, but still had the same issue when using the string field and coded domain)

All comments

MikeMillerGIS

Does you source data have Asset Group and Asset Type? If so, this tools only supports one type field and is not designed to support a UN like source.

If you have a UN like source(AG/AT), I suggest you run the Subtype To Classes tool, which will convert all your Asset Groups to FeatureClasses, then run that input into the tool and select your Asset Type as your type field.

https://esri.github.io/Utility-Data-Management-Support-Tools/docs/3.5/SubtypesToClasses.html

NathanGEOregon

Just using a standard feature class with a domain field. The field type is String, could that be the issue?

MikeMillerGIS

What version of the tool/pro are you using. We relaxed the ability to use a string as the type field in a later release.

NathanGEOregon

Pro 3.3 with the migration toolset that was provided at the ORURISA UN workshop in Portland with Robert.

MikeMillerGIS

If you look at the properties of the toolbox, it will tell you the version. I would suggest getting 3.3.3 from here:

https://community.esri.com/t5/arcgis-utility-network-blog/get-started-with-the-migration-toolset/ba-p/1590334

NathanGEOregon

Utility Network Migration 3.3.1

RobertKrisher

@NathanGEOregon can you include a copy of the log from when you ran the tool? specifically I'm wondering if there are any warning messages for that field.

NathanGEOregon

@RobertKrisher I did get this error:

Coded value domain is not assigned or has no values for VALVEFUNCTION on Water_Valve

However the input data did have a coded value domain set for the field, it was just a string field with coded values versus an integer field.

NathanGEOregon

It worked after I mapped the string data over to a new Integer field and created an Integer coded domain and re-ran the Migrate to Utility Network tool.

(I did download the Utility Network Tools 3.3.3 as Mike recommended, but still had the same issue when using the string field and coded domain)

MikeMillerGIS

Did the source class have subtypes? If you want to share the schema, I can take a look at what is going.

Rejoindre la conversation

Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.

Liens rapides

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.