Latest Contributions by MikeMillerGIS

Would be interested in seeing the same batch trace run from a script, outside pro. 30 secs a trace is not good. Nothing batch trace can do about that. I think it is the gp tool overhead of running inside pro. You have 9 maps and one active. The trace is communicating with those maps. Try it in pro with no maps, you will see a huge improvement ... View more

I reviewed the code for Batch Trace and I take back this statement"Batch trace can use the resulting lines and remove them from the trace starting points to reduce the number traces required. " Batch trace does not have this skip logic, but Build Starting Points does.  So you could run Build Starting Points and an Isolation trace to build out the starting points to trace the system.  Then run Batch Trace with that reduced set.  I will add an issue to expose that logic in Batch Trace too.  ... View more

Also very interested in why Batch Trace is taking 15 seconds a feature.  If you turn on debug mode, we can get a better idea of what is going on.   Open ArcGIS Pro Open the UtilityDataManagementSupport toolbox Open any tool in the tool box.  This loads the udms module from inside that toolbox into python/memory Open a python command prompt enter the follow:   import udms udms.logger.setLevel('DEBUG') Run Batch Trace ... View more

Batch trace can use the resulting lines and remove them from the trace starting points to reduce the number traces required. Now doing this may lead to some inaccurate results. Such as a larger area isolates pipes that could be isolated with a different set of valves. Each trace result is stored in its own file, so you would just process the results after complete. The only way we thought to reduce it was to skip calling gp trace and call the trace rest end point directly, which eliminates the gp overhead and multithreading the traces. ... View more

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

Also, many of the attribute rule we once shipped have been migrated to Data Reviewer rules or to Template Attribute Rules.  Many organizations found the included attribute rules too rigid and caused issues as they were not aware of them.   We suggest you leverage the Templated Attribute Rules provided with ArcGIS Pro and configured them to meet you editing needs. ... View more

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

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

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

You can add the proposed features to the utility network classes and snap them, but use the Lifecycle Network attribute to set them as Out of Service.  The trace will treat them as a barrier and stop traversing at that location.  The subnetwork definition has a setting to include/exclude barrier features in the definition.   ... View more

You can disable network topology and add a tier in the UN.  To add a tier in the Asset Package, you have to fill out all the tier properties, which can be a complicated process. ... View more

You can download the tools from here - https://esri.github.io/Utility-Data-Management-Support-Tools/ ... View more

If you have a propagator configured, you need to set the propagated network attribute.   ... View more