topic Re: Automatic tracing from multiple start points, exporting the results as json in ArcGIS Utility Network Questions

Automatic tracing from multiple start points, exporting the results as json

JohnGoat — Fri, 19 Apr 2024 12:14:06 GMT

Hi all,

I have 150 Low Voltage Service points for which I have TracePoints1 printed in the General Notes area. At these points, I want to produce separate json by doing upstream traces for each of them. After throwing a flag at each of these starting points one by one, it will produce json, then the first flag will be cleared, it will move to the next point, throw a flag there and produce json. The process will repeat this way for 150 starting points. How can I do that?

I want to get the AssetID parameters of the circuit breakers by generating json from 150 starting points.

I want to make a process automation for these processes from the points I marked on the map. How can I do these things with Python?

PS:

For now I'm working on Mobile gdb
ArcGIS Pro 3.1.4
UN 6

Re: Automatic tracing from multiple start points, exporting the results as json

JohnAlsup — Fri, 19 Apr 2024 10:46:42 GMT

This toolbox https://github.com/Esri/Utility-Data-Management-Support-Tools contains a tool called batchtrace. It can do what you are describing.

https://esri.github.io/Utility-Data-Management-Support-Tools/docs/3.0/BatchTrace.html

Re: Automatic tracing from multiple start points, exporting the results as json

JohnGoat — Fri, 19 Apr 2024 12:49:45 GMT

Thank you @JohnAlsup
I reviewed the toolkit but I'm getting errors, is there a source showing how it works?

Re: Automatic tracing from multiple start points, exporting the results as json

MikeMillerGIS — Fri, 19 Apr 2024 12:59:13 GMT

Can you try the version here? https://github.com/Esri/Utility-Data-Management-Support-Tools/tree/Preview3.1.2

Make sure to remove the old toolbox(best to delete it) and restart pro. If that does not work, I can pull the 3.1 code and look at a fix for that issue

Re: Automatic tracing from multiple start points, exporting the results as json

JohnGoat — Thu, 23 May 2024 07:06:51 GMT

You are right @MikeMillerGIS,

I ran the updated version and I don't get any errors. But this time I see that you have bypassed many of my starting points. I get a "No valid starting locations found" notification. When I examined the data, I could not see any problems at the starting points.

I used the parameter (notes = 'Trace1') for the starting point. I want to trace 2999 points, but as a result I get 310 output.

Re: Automatic tracing from multiple start points, exporting the results as json

MikeMillerGIS — Thu, 23 May 2024 10:29:05 GMT

Do you have different tiers in your data? What tier is your downstream trace set up for? You might need a different trace config per tier/per junction. You would need a field on the junction class with the trace config name and the code can pull the trace config from that field

Re: Automatic tracing from multiple start points, exporting the results as json

JohnGoat — Thu, 23 May 2024 11:48:24 GMT

Hi @MikeMillerGIS

There are no different tiers, I am trying to trace within the same tier. Each tracking starting point is within the same tier.

In the screenshot, starting points 317009 and 317010 are in the same tier. It gives error 317010, I do not get any errors when I trace on the map. There are many examples like this, why can't it find the starting point?

Re: Automatic tracing from multiple start points, exporting the results as json

MikeMillerGIS — Thu, 23 May 2024 11:55:11 GMT

I am not sure then. I just ran through my junctions and they worked. If you manually set a trace point at that junction and use the same trace config in the gp trace, does it work?

Re: Automatic tracing from multiple start points, exporting the results as json

JohnGoat — Thu, 23 May 2024 12:24:33 GMT

Yes, when I trace with the GP tool, I do not get an error at the same point. I don't understand this anyway

Re: Automatic tracing from multiple start points, exporting the results as json

MikeMillerGIS — Thu, 23 May 2024 12:35:11 GMT

If you put a SQL query on batch trace for that one row, does it work? What if you put default terminal Id to 1?

Does your junction layer have a field called terminalid or featureglobalid?

If you pass in the starting point layer that you used to test the trace(in default database) to batch trace, does it work?

For tracing junctions, the required fields are featureglobalid(if does not exist, batch trace looks for globalid) and terminal Id.

Re: Automatic tracing from multiple start points, exporting the results as json

JohnGoat — Fri, 24 May 2024 09:08:05 GMT

yes I have the featureglobalid field, and I saw that there were records with null values. When I calculated the empty records with Field Calculate, I completed the process without any problems.
Thank you for your interest @MikeMillerGIS
I thing If the featureglobalid field is empty, it would be better to look at the globalid field.

Re: Automatic tracing from multiple start points, exporting the results as json

MikeMillerGIS — Fri, 24 May 2024 09:14:06 GMT

I would suggest just removing the FeatureGlobalID field. It was needed in an earlier version, is no longer needed.

Re: Automatic tracing from multiple start points, exporting the results as json

JohnGoat — Tue, 23 Jul 2024 14:31:01 GMT

Hi again @MikeMillerGIS I hope you are well

I generate json using the Features result type parameter, the json content in screenshot number 1 gives me this.
I want to get the fields I specified in the json results as in screenshot number 2.

How can I do that ?

thanks,

Re: Automatic tracing from multiple start points, exporting the results as json

MikeMillerGIS — Wed, 24 Jul 2024 08:11:08 GMT

You need to generate a trace configuration that has that information. The Add Trace Configuration tool currently does not expose that information, so you need to create a Trace with Feature Output and define the fields, and use the Trace to Trace Config tool to create the Trace Configuration as this uses Import Trace Configuration and will create a trace config with the feature field and network attribute information.

Re: Automatic tracing from multiple start points, exporting the results as json

JohnGoat — Wed, 24 Jul 2024 08:19:00 GMT

@MikeMillerGIS wrote:
so you need to create a Trace with Feature Output and define the fields, and use the Trace to Trace Config tool to create the Trace Configuration as this uses Import Trace Configuration and will create a trace config with the feature field and network attribute information.

I don't understand what I'm supposed to understand, can you explain it in more detail Mike?

The add trace configuration tool only provides Selectin and Aggregated Geometry options. Does not allow field define

Re: Automatic tracing from multiple start points, exporting the results as json

MikeMillerGIS — Wed, 24 Jul 2024 08:23:40 GMT

You cannot use Add Trace Configuration. Use Trace and fill it out as you want. Then use the Trace to Trace Configuration tool in the UtilityDataManagementSupport toolbox. This uses the python syntax from trace and converts it to a Trace Configuration

https://esri.github.io/Utility-Data-Management-Support-Tools/docs/3.3/Trace2Config.html

Re: Automatic tracing from multiple start points, exporting the results as json

JohnGoat — Tue, 20 Aug 2024 08:17:42 GMT

Hi @MikeMillerGIS

Thank you for information,

I created a trace with Feature Output and define the fields. Then I was able to create a Trace Configuration with the Trace to Trace Config tool. When I try to run this configuration, I get this error. The configuration contains field definitions and the directory path information where to extract the json file.

Re: Automatic tracing from multiple start points, exporting the results as json

MikeMillerGIS — Tue, 20 Aug 2024 11:18:59 GMT

What version of pro/enterprise? Do the server logs or the ArcGIS Performance monitor provide any more details?