Good Morning!
I am attempting to understand how sewersheds work in the Utility Network. When I assign a subnetwork controller (directional manhole channel) to the upstream terminal, and assign the from/to terminal on the lines for that feature (customer does not want to use the pipe connections/associations to manage terminals), the entire collections system is designated as a sewershed.
Furthermore, when I do a shortest path trace using both the upstream and downstream terminal for the manhole channel, the results are the same. However, when I do an upstream trace doing digitized direction- I get what I would expect. Why would the behavior for an upstream terminal differ from an upstream digitized direction trace? Should I also be setting terminals on manholes further upstream? I am just trying to understand what is causing the entire network to be picked up as upstream from a given manhole- the shortest path trace seems to always trace downstream regardless of what terminal I pick for the starting point.
I will also mention the collections system tier has not been set up yet- is that a requirement for the network to be able to properly delineate a sewershed? Will also note that I do not get this behavior on all manholes- any assistance or pointers in the right direction is appreciated.
Subnetwork traces do not take the digitized direction of lines into account when traversing the network. This is why the digitized direction traces are producing a different result, and why many customers who manage sewer or storm networks often rely on those traces instead of subnetworks to perform analysis.
Shortest path traces ignore both terminal directionality and digitized direction.
If you feel that subnetworks should also support the option to use the digitized direction of lines, I encourage you (and other customers reading this) to log an issue with support and create an enhancement request for that functionality. It is something that was considered when we implemented digitized direction tracing, but we felt that customers who used those traces wouldn't want to also configure subnetworks to use the same logic.