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; } } }

Connectivity Trace - Setting up combined condition barriers

Jens_Dalsgaard

Hi there

Need to do a connected trace stopping whenever encountering a low voltage cable or a low voltage overhead line.

ElectricLine::37::Low Voltage Underground Conductor::102::AC Underground LV
ElectricLine::6::Low Voltage Overhead Conductor::100::AC Overhead LV

This is done using condition barriers - in SQL I would create a query like

(ASSETGROUP = 37 and ASSETTYPE = 102) or (ASSETGROUP = 6 and ASSETTYPE = 100)

Using the GP tool I would set it up like this:

How do i know that ArcGIS does an (A and or (C and D) and not a A and (B or C) and D?

It's the first combination / query that I need.

Finde mehr Beiträge mit dem Tag

Accepted answers

All comments

MikeMillerGIS

Jens sent me a sample dataset and was able to see what is going on.

The behavior is as designed.

When selecting a target tier in trace, the condition barriers and other parameters defined in the trace, are only applied to tracing the tier in the Tier parameter. The subnetwork definition of the target tier and all the tiers between Tier and Target tier are used. The user specified trace configuration is not applied to those tiers.

Jens_Dalsgaard

Certainly, I have sent you a mail allowing you to immediately test what works and what apparently seems to not to be working.

MikeMillerGIS

Jens,

If you want to provide a sample, I can help troubleshoot.

Jens_Dalsgaard

Creating network categories and assigning these as relevant to asset types representing cables and overhead lines works out - to some extent.

For example - I have created a new network category Volue_LV_OHUG and have assigned this to low voltage cables and overhead lines asset types.

And setting up a named trace configuration doing a connected traced yet using this network category (Volue_LV_OHUG) as conditional barrier seems to work as intended. the trace stops at low voltage cables and overhead lines.

But if I create a named trace configuration (or simply perform a trace) downstream from a medium voltage trace starting point to continue into low voltage (because I want the low voltage part of the substation included in the trace result) yet using the same network category as a conditional barrier the trace still seems to continue into the low voltage grid.

What should I look for when debugging?

MikeMillerGIS

The trace parameters do not support sql grouping, you have to rely on the AND and ORs, so it gets tricky to make a correct sql statement without group

Jens_Dalsgaard

Of course, obviously. Should have seen this myself.

Despite this, do you see any arguments against adding an idea for allowing grouping as was my initial proposal?

Adding categories will work fine in this specific case, yet in may other cases it would seem unflexible.

MikeMillerGIS

Network Categories are just tags of Asset Group/Asset Types. Just make a category and assign to all the AG/ATs that you want to stop your trace and then use that category as the condition barrier:

Jens_Dalsgaard

Please elaborate.

How may I solve the need through Categories, Mike?

MikeMillerGIS

You cannot group sql like that easily. I would suggest using a category.

Nimm an der Unterhaltung 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.