The problem statement is how do we show the flow of a resource on the map. We could do this in ArcMap with our Geometric Network. I am exploring if UN supports something like this out of the box.
Now just to confirm, my understanding is that FlowDirection introduced in UN v7 will not really help with this. This is more to do with being able to trace "upstream" and "downstream" without subnetwork controllers. This attribute needs to be set manually by the user to guide the trace.
What would be awesome is - updating the subnetwork sets the FlowDirection attribute on the line. This can be then used to visualize the flow.
So, questions -
How to people achieve this right now?
Is there a tool to SET the FlowDirection based on the flow?
https://support.esri.com/en-us/knowledge-base/faq-is-it-possible-to-display-flow-direction-arrows-us...
Solved! Go to Solution.
Setting the direction using the flow direction field does make it easy to symbolize flow direction (which is what sewer/stormwater customers often do), but it introduces a problem whereby every time you update the flow direction you need to validate the network (because it's a network attribute), then update the subnetwork.
The feature is still under consideration, but for the time being you would need to extract the connectivity for the subnetwork and parse the results (with respect to the subnetwork's definition) to determine the flow of each network element (which is finer grained than the feature).
Because this is something typically done by applications that read the utility network topology, there is a developer's being created to demonstrate an approach for how to interpret the flow direction using the JSON file.
Setting the direction using the flow direction field does make it easy to symbolize flow direction (which is what sewer/stormwater customers often do), but it introduces a problem whereby every time you update the flow direction you need to validate the network (because it's a network attribute), then update the subnetwork.
The feature is still under consideration, but for the time being you would need to extract the connectivity for the subnetwork and parse the results (with respect to the subnetwork's definition) to determine the flow of each network element (which is finer grained than the feature).
Because this is something typically done by applications that read the utility network topology, there is a developer's being created to demonstrate an approach for how to interpret the flow direction using the JSON file.
Thanks Robert!
I had a feeling I would need to do this with the subnetwork export!
Try this out
Thanks
Veer
@VeerSingh - Hi Veer, not quite what I was looking for.