So I have to deal with multiple locations for a single web feature layer that we use for tracking purposes. It would a nice and useful for our field workers to have their attribute value choices stored in a domain filtered using some sort of spatial filtering. The way I'm thinking about how this would work is like a cascading select in Survey123. I know I can set up contingent values and attributes rules to accomplish some of this, but being able to link the acceptable choices for workers would save time and make it easier for users to collect the data. While also potentially speeding up the data entry and improving data quality. The spatial filter/Domain could be created by adding a bounding box for coded domain value
So the idea is this
1)Create Spatial filter/Domain
2) Attribute value choices present to the user are limited based on the location.
3) Spatial bounding could be used as the limiting feature for each value or create a link to a particular feature class in the layer.
In my mind, it would work like this. When you have multiple properties, each with named management areas and preestablished compartments within those management areas. Property spatial attribute choice limits management area choice, and finally, the compartment potential compartments. But by using the location data, I prune the options presented to the user and potentially do it faster than have to setup new attribute rules, contingent values, etc
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.