Upstream tracing for water but taking out almost entire subnetwork

122
1
Jump to solution
04-01-2024 09:38 PM
NadiaAlami
New Contributor III

Hi everyone, we try upstream tracing using our water pipeline data, the result is like figure below where it trace almost entire subnetwork except the service line. It is correct? 

Can we trace it direct to the subnetwork controller(source) without it tracing entire subnetwork? or we misunderstand  the concept of upstream tracing in Utility Network.

Thank you in advance.

NadiaAlami_0-1712032219447.png

 

0 Kudos
1 Solution

Accepted Solutions
RobertKrisher
Esri Regular Contributor

@NadiaAlami The answer to this is similar to the answer to your other post about downstream tracing. Your water distribution system, like most, is heavily looped. An upstream trace shows you all the potential paths that water can take to get to a location, so the result returned is correct, even if some paths are only contributing a small fraction of a percent of water.

It sounds like you want to see the shortest path to your subnetwork controller, which you can accomplish by running a subnetwork controller trace then running a shortest path trace between your subnetwork controllers. The shortest path trace will find the shortest path between ONLY TWO points, so if you have multiple controllers you will need to either pick just one of them or iterate through all of them and merge the results.

View solution in original post

0 Kudos
1 Reply
RobertKrisher
Esri Regular Contributor

@NadiaAlami The answer to this is similar to the answer to your other post about downstream tracing. Your water distribution system, like most, is heavily looped. An upstream trace shows you all the potential paths that water can take to get to a location, so the result returned is correct, even if some paths are only contributing a small fraction of a percent of water.

It sounds like you want to see the shortest path to your subnetwork controller, which you can accomplish by running a subnetwork controller trace then running a shortest path trace between your subnetwork controllers. The shortest path trace will find the shortest path between ONLY TWO points, so if you have multiple controllers you will need to either pick just one of them or iterate through all of them and merge the results.

0 Kudos