ArcGIS Pro 2.5: Utility network appears not to have tools to display flow arrows and set flow direction,

[JamalNUMAN]

ArcGIS Pro 2.5: Utility network appears not to have tools to display flow arrows and set flow direction,

It would be great if the “display flow arrows” and “set flow direction” get available

ArcGIS Pro 2.5: How to display flow arrows and set flow direction in the utility network,

[HillaryBjorstrom]

@HillaryBjorstrom @BraydenSAuten @JamesRains @JamalNUMAN Thanks for the link however managing the digital direction manually seems unmanageable. are there any tools or workflows to catch these issues? like queries to select lines that need to be flipped based upon a downstream trace result? Currently i'm trying to use the enabled field as a trace stop and would like that to be the end of my feeder. my current configuration was created using the new migration to utility network tool.

[JamesRains]

@AyanPalit @HillaryBjorstrom @BraydenSAuten @JamalNUMAN 
Ayan - What you posted seems like it would work well for our gravity wastewater system, which happens to be drawn in the direction of flow. However, this will not work with our electric system due to switching changes that can redirect flow based on the Enabled field being True/False. I know that we can run a trace on the network to show connectivity but all the steps we have to jump through just to do that, especially when doing multiple edits, gets exhausting after a while. In ArcMap, if something wasn't connected properly, the flow direction arrow would automatically change to a solid dot. To verify you had it connected, all you had to do was click the Set Flow Direction button and it either changed to an arrow or stayed a dot, letting you know something was wrong with connectivity. Not having that simple function/tool has cost my editors a lot of time and effort.

[AyanPalit]

@JamesRains Thanks for reviewing the option documented at Introducing Tracing Using Digitized Direction in the Utility Network

Looks like this meets the requirements partially - gravity-based networks. The use case for dynamic network with switching changes (electric) or pressurized hydraulic flow (gas) is important as well.

Now that Utility Network does have a network attribute called ‘FLOWDIRECTION’, that can be leveraged to support the dynamic use case. Perhaps, a script/attribute rule can be added to update the ‘FLOWDIRECTION’ and this will allow for the symbology to automatically refresh.  Thinking out loud here so, additional gaps should be documented. 

[HillaryBjorstrom]

i like the attribute propogation idea. i will see if i can figure that out. any documention on setting up propogation would be greatly appreciated.

[JamesRains]

@AyanPalit Thinking out loud is good. It offers more topics and ideas to inspect and research. The FLOWDIRECTION idea sounds cool. However, according to documentation on Configure A Trace it specifically states, "Do not use this option if you are currently modeling flow using subnetwork controllers." Our ElectricUN is based on Subnetwork Controllers so it doesn't look that the FLOWDIRECTION would be an option either.

Please keep thinking out loud though and hopefully a solution can be found for adding Flow Direction Arrows into the Utility Network.

[JamesRains]

@AyanPalit @JamalNUMAN @BraydenSAuten @HillaryBjorstrom 
Some afterthoughts... We don't have any issues with tracing our Electric system in the Utility Network. We can set starting points and use the OOTB tracing along with custom Trace Configurations that work great. This has to do with (1) visual connectivity while editing and trouble shooting, (2) visual flow direction for quickly seeing how/where things are being fed.

ArcMap:

ArcPro:

Again, I can't reiterate enough that this is a vital tool our editors used daily in the GN. When someone from the electric department or management would come over and ask us to show them how the system is being fed, we would be able to show them because of the Flow Direction Arrows. When the system wasn't flowing properly in our 3rd party modeling & OMS software, we could visually see where the problem was and fix it in a timely manor.

Please help us all by getting this idea moved from "Under Consideration" to "In Product Plan".

Thanks again!