Latest Contributions by MikeMillerGIS

The manhole channel is a device that connects to pipe connections. It is contained by the structure junction manhole. If you do not want to model Z values on the pipe, then you do not need to use the pipe connections and the structure junction manhole. Many have done this, you might just need to add the rule to allow manhole channel to connect to pipes. We incorporated this feedback when building the essentials model, where the manhole channel was just called manhole and pipes snapped directly to it. Hope this helps. ... View more

The vaults are in the structure network and you cannot have a Junction Edge rule from the structure network to the domain network.  The Manhole channel is contained in the structure.  The manhole channel is connected to the pipes and allows flow from pipe to pipe.  If you are modeling Z on mains, you will need to use a pipe connection at the end of each pipe and then connect the pipe connections to each other or through the manhole channel.   The essential version of sewer, does not use the Z's on pipes and provides a more Geometric style modeling of sewer   ... View more

Why is the 'Interescts($feature)' a string?  Dont think you need filter at all  change to var intersectingPolygons = Intersects(demFeatures, $feature); ... View more

please post code using the insert code sample option // Retrieve the DEM polygons feature set var demFeatures = FeatureSetByName($datastore, "Elev_Polygons_2023", ["gridcode"], true); // Find the polygons that intersect with the current device var intersectingPolygons = Filter(demFeatures, 'Intersects($feature)'); // Get the first intersecting polygon var intersectingPolygon = First(intersectingPolygons); // Extract the gridcode value if an intersecting polygon exists var elevation = intersectingPolygon["gridcode"]; // Return the elevation value return elevation; ... View more

Jens sent me a sample dataset and was able to see what is going on.   The behavior is as designed.   When selecting a target tier in trace, the condition barriers and other parameters defined in the trace, are only applied to tracing the tier in the Tier parameter.  The subnetwork definition of the target tier and all the tiers between Tier and Target tier are used.  The user specified trace configuration is not applied to those tiers. ... View more

Jens,    If you want to provide a sample, I can help troubleshoot. ... View more

It appears, according to the help, that the deleted subnetwork does not get purged from the subnetwork table unless you run Export Subnetwork or Update Subnetwork in Default. ... View more

Can you post a screen shot?  What version of the ArcGIS Pro? Mine seems to be working:   ... View more

The trace parameters do not support sql grouping, you have to rely on the AND and ORs, so it gets tricky to make a correct sql statement without group ... View more

Network Categories are just tags of Asset Group/Asset Types.  Just make a category and assign to all the AG/ATs that you want to stop your trace and then use that category as the condition barrier:   ... View more

or change your slashes, but you def need the f.  Try this: f"{wDB}/WaterLine" or f"{wDB}\\WaterLine" ... View more

Just a comment on Josh's code.  Calling Count and then First results in an extra query.  For optimal performance, just call First and check if the result is valid.   var xs = Intersects($feature, someOtherLayer) var intersected_feature = First(someOtherLayer) if (IsEmpty(intersected_feature)){ return 'No Intersecting Feature Found' } return intersected_feature['other_attribute'] ... View more

You cannot group sql like that easily.  I would suggest using a category. ... View more

Wrong data type. The field has an invalid data type. A field has been assigned the wrong data type. For example, an integer data type for the field was expected instead of a string data type. https://pro.arcgis.com/en/pro-app/latest/help/data/utility-network/about-error-features.htm#ESRI_SECTION1_B9C576CB6CA8492F9B0E0FC822BDE315   ... View more