Timeline for Using weight in geometric network to Find Path Upstream
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 27, 2015 at 2:01 | vote | accept | Duc TN | ||
| Jul 25, 2015 at 16:12 | comment | added | Duc TN | I see, @hornydd. At first, I thought the Find Path Upstream is the same with Find Path except in the Find Path Upstream we always have a source/sink as a flag junction. Anyway thank you so much :) | |
| Jul 24, 2015 at 9:18 | comment | added | Hornbydd | I used the geometric network editing tool to disconnect a line in my network so it became undetermined and can confirm the find path upstream would not trace the shortest route, so @FaridCher is right you need to ensure those edges are connected and have their flow direction set. | |
| Jul 24, 2015 at 3:50 | comment | added | Duc TN | Well, I can't, it must be established based on the Source. Okay so the thing is Find Path Upstream only work with determined edges. Hmm I see it now. Thanks Farid, I think I have to find another solution for this | |
| Jul 24, 2015 at 3:32 | comment | added | Farid Cheraghi | This is the reason that Find path works and Find Upstream or Find Downstream won't work with your situation. If you establish flow directions based on digitized direction you will get the for those indetermined edges | |
| Jul 24, 2015 at 3:05 | comment | added | Duc TN | Thanks Farid, but in ArcGIS Resources said that weight can be used with Find Path Upstream trace task. So if it must be used with the determined direction network, maybe we don't need weight (because the path is unique in this case) | |
| Jul 24, 2015 at 2:54 | comment | added | Farid Cheraghi | Please value the effort of others that are helping you by up-voting and marking the "Correct Answer". See tour(www.gis.stackexchange.com/tour) | |
| Jul 24, 2015 at 2:44 | comment | added | Farid Cheraghi | When the terms upstream and downstream are used with network trace solvers (like Find Path Upstream), all network directions must be set and determine. The trace will stop at edges that are undetermined or uninitialized. | |
| Jul 24, 2015 at 2:40 | comment | added | Duc TN | Hi Farid, I did set the flow direction, you can see the Source junction in the snapshot. The point is from those indeterminate edges, so does the Find Path Upstream can't solve in that case | |
| Jul 24, 2015 at 2:23 | comment | added | Farid Cheraghi | Based on the snapshot you shared, you need to establish flow directions based on the AncillaryRole Field. There are some indeterminate edges on your graph. | |
| Jul 24, 2015 at 2:15 | comment | added | Duc TN | Thanks Farid, I did exactly as you said but this can only work with Find Path, but I want to use the Find Path Upstream, any idea please? | |
| Jul 24, 2015 at 1:20 | history | answered | Farid Cheraghi | CC BY-SA 3.0 |