Hi @YatharthSahXIG
1. Visibility Control
ArcGIS Field Maps doesn’t natively filter features based on real-time GPS location. However, you can simulate this behavior using:
Geofences + Location Alerts
• You can define a 100-meter geofence around each feature or area.
• When users enter the geofence, Field Maps can trigger a location alert.
• This doesn’t hide features, but it can notify users when they’re near relevant data.
Custom Arcade Expression for Visibility
• You can use an Arcade expression in the layer’s filter or form visibility logic to compare the user's location to the feature’s geometry.
• Example logic:
var userLocation = $location;
var featureLocation = Geometry($feature);
var distance = Distance(userLocation, featureLocation);
return distance <= 100;
This can be used to hide fields or forms, but not entire features from the map view.
2 Editing Restrictions
This part is more feasible and elegant:
Arcade Expression in Form Editing Logic
• In Field Maps Designer, you can configure the form logic to make features non-editable if the user is too far.
• Use an Arcade expression like:
var userLocation = $location;
var featureLocation = Geometry($feature);
var distance = Distance(userLocation, featureLocation);
if (distance > 100) {
return false;
}
return true;
This disables editing and can be paired with a custom message like:
- “You’re too far to edit this point. Get within 100m.”
There is a community post which you may find helpful also.
Solved: Field Maps editing restriction - Esri Community
I hope this helps you in some way.
