The Filter by Geometry tool filters features by a spatial relationship with other features in the same feed or those of another feed or dataset. Features for which the spatial relationship evaluates as true are retained.
- A real-time analytic uses the Filter by Geometry tool to retain only the incoming records from a feed where the feature geometry intersects a polygon dataset of port areas.
- A big data analytic uses the Filter by Geometry tool to retain only features where the feature geometry enters a polygon dataset representing service areas.
- Determine when shipping vessels from one feed are inside a moving severe weather cell from another feed.
- The tool can compare the spatial relationship of features to point, line, or polygon features.
- The tool evaluates a user-defined spatial relationship between the target features and a specified join dataset.
- If a Spatial Relationship of enter or exit is selected, then checking First observation can trigger enter or First observation can trigger exit indicates that the first target feature received satisfies the filter condition if it is inside any join feature in the case of enter or outside all join features in the case of exit, despite having no prior target feature to which to compare the current target feature's location. The default is false (unchecked).
- If the Spatial Relationship parameter is set to enter or exit in a real-time analytic, the tool will operate in a stateful manner which enables it to compare sequential observations to one another to detect a change in state, for example, is a current condition different from that of the previous observation. With other spatial relationships in real-time analytics, the tool does not need to compare any observations with previous ones so it can run in a stateless manner which is less resource intensive.
- The Target Time Window parameter in a real-time analytic should be set to at least as long as the longest anticipated interval between observations for any given track. Observations older than this duration will be purged from memory in order to manage resources.
- If a feed is connected to the join port, distance calculations will be done dynamically based on the changing features in both the target and join feeds.
- In dynamic geofencing, the Join Time Window parameter must be set. If the join feed does not have a field tagged as END_TIME and the last known observation for a join feature is older than this window, it will be purged from the tool's memory and will not be included in the analysis. If the join feed has a field tagged as END_TIME, the feature will age out of the geofence store according to the value in the field tagged as END_TIME or at the close of the join time window, whichever comes first.
- Join feeds must have a TRACK_ID configured.
- Adding a join feed to a tool must be done in the model view. Analytics with tools using join feeds cannot be viewed or edited in the workflow view.
- Dynamic geofencing is in beta for most configurations. The only currently released configuration is for Join Features. Configurations leveraging beta capabilities should not be used in production workflows.
Specifies the layer which will be filtered.
Specifies the layer to process a spatial relationship against.
Specifies the criteria used to spatially filter the target features. Spatial relationships include:
Target Time Window
When operating in a stateful manner, this parameter specifies the longest anticipated period of time between observations for each track.
Join Time Window
The time window for the join feed (dynamic geofences). If the last known observation for a join feature is older than the time window specified, it will be purged and will not be included in the analysis. If the join feed has a field marked as END_TIME, this parameter is optional.
Dynamic geofencing is currently in beta and should not be used in production workflows.
The Filter by Geometry tool does not alter incoming features, so the output layer will contain the same fields and attribute values as the incoming features.