Latest Contributions by RobertKrisher

If you consider the main part of your stormwater system to be 'connected', then there are several ways you could describe these features. You could say they are disconnected (from the main system), they are islands of connectivity, or they are disjoint sets of features. The term subnetwork is used by the utility network to mean something very specific; a subnetwork is the collection of features that are traversable to a subnetwork controller. In the case of stormwater systems, its every feature that is traversable to an outfall or outlet. To identify these features in a trace network, you could set starting points on all your outfalls/terminal discharge locations, then run an upstream trace (Trace (Trace Network)—ArcGIS Pro | Documentation). Switch the selection set on all your network layers (Select Layer By Attribute (Data Management)—ArcGIS Pro | Documentation with the SWITCH_SELECTION option). This would give you the collection of all the features that have no outlet, and is a good place to start for a reasonable amount of effort. If you wanted to find all the distinct islands, you could do a connected trace for every line (or device or junction) in the network, output the JSON, and parse the elements to see how many features are connected to it. As you iterate through the features and results, keep track of which features you've already discovered so you don't trace the same feature more than once. ... View more

You use attachment and containment associations to create relationships between structure and domain features that allow you to see which structures are supporting which subnetworks or to include them in your trace results. If you have a device attached to the pole this will happen automatically, but if you don't have any other equipment at a pole you can place a junction feature on the line then attach that junction to the pole. In the electrical model these are line ends and attachment junction features. ... View more

This topic is discussed in this article: https://community.esri.com/t5/arcgis-utility-network-blog/best-practices-for-working-with-utility-network/ba-p/1339979   You have a lot more control over how features appear through using a web map than you do with a map service, and this is the recommended approach. Each service you publish also consumes additional resources on the server. Publishing 100 different services to support 100 different maps is not scalable but publishing 1 service that is used by 100 maps is. You typically maintain a small number of features services that expose your enterprise data (see above article), then your web maps provide different experiences on top of these services. ... View more

Your problem is that you assumed that the transformer was going to be at the first vertex of the line when it is in fact at the last vertex of the line. It is 100% acceptable for the transformer to be at the last vertex of the line because the utility network doesn't rely on the digitized direction to control flow, and electrical networks don't rely on the digitized direction of lines to control flow/tracing. If we did, then you wouldn't be able to backfeed a circuit by opening a switch because all the medium voltage lines would be drawn in the wrong direction. The flowdirection is unrelated to that error, and even if you were to deploy a v6 network without the attribute you would still have the error. The problem is that you have populated the fromdeviceterminal with the terminal id of the device at the todeviceterminal position of the line. Remember that fromdeviceterminal and todeviceterminal refer to the device at the first vertex (from device) and the last vertex (to device) of the line, and not related to the flow of the network (i.e. which device is upstream). ... View more