Select to view content in your preferred language

Attribute Assistant Intersecting Feature Method -> Attribute Rule?

1038
3
Jump to solution
09-29-2022 03:57 PM
Labels (2)
Steve_SchunzelAtTacoma
Occasional Contributor

Hello,

I'm trying to convert from using Attribute Assistant to Attribute Rules and I'm struggling with one of my old rules built with the INTERSECTING_FEATURE method.  Here's the problem:

I'm mapping parking blocks and I need to pick up the street name of the longest intersecting street segment (S 19th St in the simple illustration below)

Steve_SchunzelAtTacoma_0-1664491802080.png

The ArcMap/AA method worked beautifully and seemed to pick up the longest edge most of the time.  However with the new Attribute Rule that I set up (using Pro 3.0), it seems to pick up the other streets that it intersects with, even if it's just one vertex (COURT D or FAWCETT AVE above).  When I loop through all the features it seems random, so I can't use the FIRST function. 

I think I'm still not understanding the fundamentals about how the Intersects function works.  Does anyone have any suggestions on how to filter out the street segment with the longest intersecting edge?

Thank for you thoughts and suggestions!

Here's my code:

//Cycle through all intersecting streets and return street name
var streetLayer = FeatureSetByName($datastore,"baseStreetCenterline", ["ST_NAME"]);
var searchDistance = 0;
var streetIntersect = Intersects(streetLayer, $feature);
var cnt = Count(streetIntersect);

var name = Null
if (cnt > 0) {
    for (var street in streetIntersect) {
        name = street.ST_NAME;
        }
    }
else {
    // pass no features found within search distance, name remains null
}
return name;

Steve Schunzel, GISP
Enterprise GIS Technical Lead
City of Tacoma | Information Technology
0 Kudos
1 Solution

Accepted Solutions
JohannesLindner
MVP Frequent Contributor

Intersects() finds all intersecting features. In the next step, you have to get the actual Intersection() and find the longest one.

// find intersecting streets
var streetLayer = FeaturesetByName($datastore, "baseStreetCenterline", ["ST_NAME"], true)
var streetIntersect = Intersects(streetLayer, $feature);

// find the street with the longest intersection
var name = null
var max_length = -1
for (var street in streetIntersect) {
    // get the intersection
    var segment = Intersection($feature, street)
    // get the intersection's length
    // if the line and polygon only touch at one vertex, segment will be null
    var segment_length = IIF(segment == null, 0, Length(segment))
    // compare to max_length, set name
    if(segment_length > max_length) {
        max_length = segment_length
        name = street.ST_NAME
    }
}
return name

Have a great day!
Johannes

View solution in original post

3 Replies
JohannesLindner
MVP Frequent Contributor

Intersects() finds all intersecting features. In the next step, you have to get the actual Intersection() and find the longest one.

// find intersecting streets
var streetLayer = FeaturesetByName($datastore, "baseStreetCenterline", ["ST_NAME"], true)
var streetIntersect = Intersects(streetLayer, $feature);

// find the street with the longest intersection
var name = null
var max_length = -1
for (var street in streetIntersect) {
    // get the intersection
    var segment = Intersection($feature, street)
    // get the intersection's length
    // if the line and polygon only touch at one vertex, segment will be null
    var segment_length = IIF(segment == null, 0, Length(segment))
    // compare to max_length, set name
    if(segment_length > max_length) {
        max_length = segment_length
        name = street.ST_NAME
    }
}
return name

Have a great day!
Johannes
Steve_SchunzelAtTacoma
Occasional Contributor

You're a genius Johannes!!  That works perfectly, thank you!!

Steve Schunzel, GISP
Enterprise GIS Technical Lead
City of Tacoma | Information Technology
0 Kudos
GelcysWilliams
Regular Contributor

Has anyone been able to figure out how to set this up referencing boundary layers in another database?  Attribute Assistant could do it in the map, but since Attribute Rules are in the database, it can only look at other layers in the same database.  I'm not adding the parcels, neighborhoods, zip codes, addresses, municipalities, and county boundary to each database where we edit to make something work in Pro that worked in ArcGIS Desktop...