topic Re: Calculate From and To Endpoint IDs (from one of several point feature classes) in Attribute Rules Questions

Calculate From and To Endpoint IDs (from one of several point feature classes)

NathanGEOregon — Fri, 01 Mar 2024 20:46:41 GMT

We are still using the Geometric Network in ArcMap, along with Attribute Assistant (AA). We are in the process of exploring a transition to the Trace Network and adopting Attribute Rules in Pro.

We have been using a couple of AA rules to populate a FromID and ToID field with the IDs of the endpoints of a line segment (Sewer Mains) from several possible point feature classes (manholes, nodes, etc).

The From Junction Field (and similar To Junction Field) in AA method made this pretty straightforward, as it would select whatever point feature happened to be at the start or endpoint and grab the associated ID, regardless of what feature class the point happened to be from.

Is there a similar way to use junctions in Arcade to supply From and To IDs to a line from several possible point feature classes? It seems if you're only working with a single point feature class, it would be pretty straightforward (https://www.youtube.com/watch?v=ueckrlhto0Q) but for multiple point feature classes, it seems you'd need to create a feature variable for each point feature class, and parse through them like "If there is a manhole point at the From location, grab the ID, Otherwise check if there is a node at the From location and grab the ID" etc.

Re: Calculate From and To Endpoint IDs (from one of several point feature classes)

MikeMillerGIS — Mon, 04 Mar 2024 11:27:46 GMT

We created a chart of AA methods to AR

https://github.com/Esri/arcade-expressions/blob/master/Attribute%20Assistant.md

The https://github.com/Esri/arcade-expressions/blob/master/attribute_rule_calculation/CalcJunctionFields.md rule should work for you.

Re: Calculate From and To Endpoint IDs (from one of several point feature classes)

NathanGEOregon — Mon, 04 Mar 2024 20:44:18 GMT

Thanks-

I did see that.

The Calculate Attributes by Junction points to a single feature class (Manholes) as possible Main endpoints. So it appears that if the endpoint could be one of many point feature classes (Manhole, Node, Valve, etc) then you would need to call in each point feature class and loop through them. I was trying to avoid this, as the Arcade code would start to get pretty bloated.

Re: Calculate From and To Endpoint IDs (from one of several point feature classes)

VanessaSimps — Fri, 15 Mar 2024 23:42:56 GMT

This is GREAT!! Thank you, such a helpful resource.

Re: Calculate From and To Endpoint IDs (from one of several point feature classes)

Bud — Sat, 16 Mar 2024 03:16:48 GMT

Re: Calculate From and To Endpoint IDs (from one of several point feature classes)

avonmoos — Thu, 09 May 2024 17:50:31 GMT

Did you end up figuring this out for many points? Example code? Thanks!

Re: Calculate From and To Endpoint IDs (from one of several point feature classes)

avonmoos — Thu, 09 May 2024 18:20:51 GMT

@RhettZufelt any ideas?

Re: Calculate From and To Endpoint IDs (from one of several point feature classes)

RhettZufelt — Thu, 09 May 2024 19:48:40 GMT

Have not really looked into this yet as the Trace network is so limited, really has no use case for us at the moment. (at least as long as ArcMap is still going)

I have a post here about doing something similar with Python that could be converted pretty easy with some of the AA rules that @MikeMillerGIS posted above.

Would have to experiment with the points coming from different dataset and see just how much of a performance hit that causes.

I originally set this up for offline use, so my nightly script just combines the manholes and cleanouts (MH's, CO's, Inlets, Outlets, etc. for the Storm layers) into a single point featureclass with the FacilityID and record number. Then, I just have my script check the intersection with this layer at the upstream and downstream ends of the line.

Since all I need is the attributes from the points that intersect, this has been working great.

Figure when I move to Pro for this, will just modify this Arcade code to intersect against this same 'combined' featureclass as it keeps things simple. Then I may test performance hits comparing this to actually intersecting the start/end points with multiple featureclasses.

Re: Calculate From and To Endpoint IDs (from one of several point feature classes)

avonmoos — Mon, 13 May 2024 14:03:02 GMT

Thanks for the info Rhett!

Re: Calculate From and To Endpoint IDs (from one of several point feature classes)

RhettZufelt — Thu, 13 Jun 2024 17:35:57 GMT

@avonmoos

With the help of @MikeMillerGIS I was able to come up with something along these lines.

Set up for my Storm data, the 'endpoints' of a gravity main can be a Manhole, Inlet, Outlet, Cleanout, Discharge Point, Network Structure, or Fitting all of which are in their own featureclass.

Though, have not tested it extensively, should be a good starting point as it is working as expected.

This will find the FacilityID from the upstream and downstream points if exist, populate the UpMH and DownMH fields in the gravity main feature class as well as update the gravity main FacilityID to UpMH-DownMH regardless of which point FC it is in.

Re: Calculate From and To Endpoint IDs (from one of several point feature classes)

NathanGEOregon — Tue, 21 May 2024 17:31:50 GMT

Thanks for doing the heavy lifting! This looks like what I had in mind!

Re: Calculate From and To Endpoint IDs (from one of several point feature classes)

MikeMillerGIS — Tue, 21 May 2024 18:22:15 GMT

We are still working on these tools, but take a look at this toolbox.

https://github.com/Esri/arcade-expressions/blob/master/attribute_assistant/AttributeAssistant.atbx

We are working on GP tools to create the arcade for you. Lots to do still(hence not really sharing them yet), but they are functioning.

https://github.com/Esri/arcade-expressions/blob/master/attribute_assistant/readme.md

NOTE: The output is a csv that you need to import, so it does not apply the AR

Re: Calculate From and To Endpoint IDs (from one of several point feature classes)

avonmoos — Wed, 29 May 2024 21:24:07 GMT

In Attribute Rules I'm only able to update 1 attribute at a time so I made one code for BeginningStructureID and one for EndingStructureID. Here is one of the codes that I came up with based on the example you provided.

Re: Calculate From and To Endpoint IDs (from one of several point feature classes)

RhettZufelt — Wed, 29 May 2024 21:55:24 GMT

True if you are just returning a result, but AR allows you to return a dictionary of keywords and update multiple attributes at once. Not real intuitive in my code as I add items to the attributes variable and return that as the 'attributes': keyword in the result dictionary.

Take a look here, an easier example to see how to return values for multiple attributes from on rule.

Re: Calculate From and To Endpoint IDs (from one of several point feature classes)

avonmoos — Wed, 29 May 2024 22:53:32 GMT

Wow, I didn't know we could do multiple at once. I'll take a dive into that and play around with it. Thanks again for the info!

Re: Calculate From and To Endpoint IDs (from one of several point feature classes)

RhettZufelt — Thu, 13 Jun 2024 17:35:28 GMT

To make it a bit easier to get a grasp of, I have modified the code to use a results dictionary without the interim dict. This should make it easier to follow:

UpMH, DownMH, and FACILITYID are the column names in the main line FC.

Re: Calculate From and To Endpoint IDs (from one of several point feature classes)

RhettZufelt — Wed, 29 May 2024 23:25:28 GMT

Also, when returning a dict, there is no need to choose a field in the AR pane.

However, there is a bug, and if you want to use this data in ArcGIS Server less than version 10.9, just populate the "Field" box.

As you can see by the minimum version required. The ONLY difference between these two rules is that I picked the FacilityID field in one. However, it will still populate all the fields in the result dict.

Re: Calculate From and To Endpoint IDs (from one of several point feature classes)

NathanGEOregon — Mon, 17 Jun 2024 16:08:56 GMT

@RhettZufelt this is fantastic, works like a charm! I was getting a "null geometry" error when validating in the Expression Builder. I simplified the the lines related grabbing the origin and endpoints of the line, which seemed to resolve the error.

var orig_point = line_shape.paths[0][0]

var end_point = line_shape.paths[-1][-1]