Field Maps Field Calculation error

TaylorGreenup

I have a data collection layer with a field for Trail ID that I would like to have auto-populate from the Trail ID field of the trails layer that I have in the same field map. These are separate layers within the same web map. I found this post and modified the calculated expression for populating this Trail ID field to the Arcade expression below (with a change from $datastore to $map to select the trails layer). This passed the error test in AGOL but when I try to do a test data collection in the Field Maps app, I get a calculation error. Does anyone have any ideas how I can get this to work? 

 

var trailLayer = FeatureSetByName($map,"R1 EDW Trail NFS Publish", ["TRAIL_NO"]);
var searchDistance = 50;
var trailIntersect = Intersects(trailLayer, BufferGeodetic($feature, searchDistance, "feet"));
var cnt = Count(trailIntersect);

var minDistance = Infinity;
var name = Null
if (cnt > 0) {
    for (trail in trailIntersect) {
        var dist = DistanceGeodetic(trail, $feature, "feet");
        if (dist < minDistance) {
            name = trail.TRAIL_NO;
            minDistance = dist
        }
    }
} else {
    // pass no features found within search distance, id remains null
}

return name;

 

 

TaylorGreenup

Hi Kathy! The thanks is really all to my co-worker David Hood who's been helping me with Arcade expressions. I've set these expressions for use in Field Maps on a point and line layer collecting information on trail features. I am having the folks in charge of the data collection effort test this before field season hits in earnest.

Yes it does calculate in Field Maps and apparently these expressions do not work in Map Viewer (tells you that when you set them up). Other limitations that we are aware of are the following: 1) it looks for the trail ID within 100ft of the collection site, 2) if you are near a junction it's going to populate with the trail ID that's higher up in the record list, 3) the record isn't editable so it can't be manually overwritten in the field (that's a function of using an expression to calculate it). So we may want to tweak the search radius and also have data collectors comment if they are near a trail junction so those will get flagged for QAQC. Or we might pull the expression out. I'm hoping the data organizers can do enough testing to be confident that having this calculation is preferrrable to manual entry. Thanks!