Batch trace - How to get count and write this to starting points

[Jens_Dalsgaard]

Hi there

I have a feature class populated with trace starting points.

I have a trace configuration returning only meters downstream of the trace starting point.

And I am able to successfully execute a batch trace using the geo-processing tool as long as I am only returning aggregated geometries.

The result is a feature class showing downstream meters (point features) that I may symbolize by the group field (Start_ID).

So far so good. I am struggling to make the next step, though.

Hence, I actually do not need the aggregated point features.

Instead, what I need is to have the batch tracing tool count all meters encountered downstream of each trace starting point and write this count to the Meter_Count attribute (LONG) in the trace starting point feature class. 

I am aware of the documentation (https://esri.github.io/Utility-Data-Management-Support-Tools/docs/3.1/BatchTrace.html) as well as on the video-walk-through (https://esri.github.io/Utility-Data-Management-Support-Tools/help/BatchTrace.mp4). 

I cannot seem top get my head around how to actually accomplish, what I want, though.

Yeah, it comes down to ticking off the Calculate option - but after that, I am left not really finding the documentation / demonstration or with a brain unable to understand the approach.

Help, please 🙂

[Jens_Dalsgaard]

Fully agree, Robert. 

Yet, working with utilities I bet you know that not all questions are fit for standard configurations.

Network categories is for standard config's and we are currently working with Elvia til finalize network categories and attributes. This - counting downstream meters - is a standard question. 

For more ad-hoc questions, other approaches likely will be pursued.

[RobertKrisher]

@Jens_Dalsgaard  Ah yes, solving for the ad-hoc scenario. Ideally, you set up network categories (and even trace configurations) to cover 80-90% of your use cases (doing this at the asset group level is a good start).

Then, a user needs to fine-tune the results in an ad-hoc trace that isn't already covered the user can add additional conditions to cherry pick specific asset types. Network Source, Asset Group, and Asset Type are all network attributes that you can include in conditional expressions on v6 or later networks. Setting up network categories for asset groups lets you skip having to make the user memorize network source ids and subtype codes which are not easily discoverable to an end user.