nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

SubnetLine covers whole network but Upstream/Downstream Trace does'nt reach to/from controllers

Rohanrajan

Update Subnetwork creates aggregate geometry of subnetwork successfully. Subnetwork Trace selects all the features in the subnetwork. But when tracing upstream from a point it stops halfway and does not reach the controller.

Similarly downstream trace stops with a feature and the next line feature is snapped and they are of same Asset Group and Type, direction is same for both lines

Tested with flow direction attribute toggled from With Digitized to Indeterminate and back.

The point feature is a Junction feature with all connectivity rules present

What could possibly stop the trace at such location.

Any insights would be much appreciated.

Thanks

Finde mehr Beiträge mit dem Tag

Accepted answers

All comments

MikeMillerGIS

Subnetworks use controllers to determine directionality. If you are using the check box to use digitize direction, then the up/downstream can produce different results since it is using the digitized direction of the line versus the controller.

Rohanrajan

We are not using the digitized direction option at all. All traces are based on subnetwork definitions only

Jens_Dalsgaard

A thought - what traversability condition barriers is the upstream trace configured with?

Could it be, that junction feature asset group / type has an assigned category used as barrier?

RobertKrisher

The junction doesn't appear to be selected, so the line is probably a barrier. If you are modeling z-values in your geometry make sure that end point of the line is actually snapped to the juction.

GIS_kiwi4

@Rohanrajan - The connectivity seems okay as the subnet line selects everything.
Are you using Trace Configurations? One thing to test would be to do a downstream trace using the same Traversibility/condition barriers as the subnetwork definition and then it should look exactly like the subnetwork trace.

If it doesn't behave the same way then I would chalk it up to the Traversibility/condition barriers in the trace.

Rohanrajan

There is no barriers at all in the tier definition neither in the traces I run.

No Categories of any asset are used in barriers in this tier definition.

All the features are at same Z. And the lines are snapped with the junctions and devices.

RobertKrisher

@Rohanrajan if you select the junction and move it, do both lines come with it?

Rohanrajan

Yes, they do.

RobertKrisher

@Rohanrajan in your screenshot it appears that the line is selected by the junction is not. this implies that the connectivity is stopping at the LINE and not the junction. Use an aggregated geometry result type to see exactly where the trace is stopping. It's possible the line is a barrier, or that there is a barrier feature drawn midspan on the line.

Nimm an der Diskussion teil

Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.

Schnellzugriffe

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.