You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Lexie asked if, rather than having the entire Oil and Gas Wells data layer to start with, if it can be limited/filtered/queried to only include the features that are within the layer's filters. If possible, we'll then need to think of a descriptive name so it's not purporting to be the full oil and gas wells data set.
the oil and gas wells layer has a ton of features in it - and most of those features are features that we don't care about or use for air quality purposes. I'm wondering if we can remove those unnecessary features from the map entirely...and reduce the number of features in the layer to only those in the filter.
The text was updated successfully, but these errors were encountered:
@nathankota I think that we should suggest an AGOL hosted feature view as the solution to this issue rather than adding another column to the config spreadsheet for a default definition query. The docs make it seem pretty simple and straightforward to create them. But they have to be created by the original owner of the AGOL item. Here's the current hosted feature service that we are using:
Lexie asked if, rather than having the entire Oil and Gas Wells data layer to start with, if it can be limited/filtered/queried to only include the features that are within the layer's filters. If possible, we'll then need to think of a descriptive name so it's not purporting to be the full oil and gas wells data set.
The text was updated successfully, but these errors were encountered: