FeatureFenceParameters Class

Detailed Description

The features that create a FeatureFenceParameters provide a set of geometries (and attributes) that define targets for the Geotrigger. For example, if the condition is "notify me when my position comes within 50 meters of one of my target areas", the fence data are "my target areas" and each Feature is one target area.

Create a FeatureFenceParameters using a FeatureTable. The features can have point, line, or polygon geometry. For points and lines, you must also supply a FenceParameters::bufferDistance. Each feature in the table represents a single fence.

You can filter features using attributes or geometry by supplying a where clause. For example, you could further refine "my target areas" to be "my target areas that are open and are in California".

The number of features fetched by querying an online table is limited by the layer's ArcGISFeatureLayerInfo::maxRecordCount. Service feature tables that support pagination ArcGISFeatureLayerInfo::isSupportsPagination are not subject to the maximum feature count limit.

A FenceGeotrigger can also take into account floors within buildings. If the feature table used to create the FeatureFenceParameters is referenced by a FeatureLayer that is FloorAware, and the AbstractLocationDataSource used to create the GeotriggerFeed includes LocationSourcePropertiesKeys::floor information, then fences will only be entered when they are intersected by a Location on the correct floor. If the fence or location data does not include valid floor information, the floor is ignored and the fence is entered when it is intersected by the location.

A floor aware feature layer or table must be part of a GeoModel that includes a valid GeoModelFloorDefinition. All layers and tables that are used by the floor definition are loaded when the GeotriggerMonitor is started.

A Location can contain the floor property as part of Location::additionalSourceProperties. This is populated automatically by IndoorsLocationDataSource, or can be supplied as part of your own implementation.

A GeotriggerMonitor accounts for changes to the featureTable while the geotrigger is active. Added, removed, or updated fence features trigger a notification by the geotrigger monitor when the updated feature meets or no longer meets the geotrigger condition.

Updates to the featureTable occur in the following situations:

• An edit (add, update, or delete) is submitted to the local feature table.
• User interactions, like performing a pan or zoom in a map or scene, request updates from an online feature table (ServiceFeatureTable) for the new visible extent.
• If FeatureLayer::refreshInterval is set on a layer associated with the featureTable, feature fences are updated at the specified interval. For a ServiceFeatureTable, fence features requested from the server include features within the buffered visible extent as well as features near the current device location. This allows the geotrigger monitor to check fences both inside and outside of the current visible area.
• Online feature fences are explicitly requested using ServiceFeatureTable::populateFromServiceAsync(const Esri::ArcGISRuntime::QueryParameters&, bool, const QStringList&, QObject*). Use this method to control how and when feature fence updates are requested from a server. Setting the clearCache parameter of this method to true clears fence features from the local feature table before repopulating with updated features from the server. This ensures that deleted features are recognized and that the geotrigger monitor sends exit notifications.

Dynamic feature fence capabilities are enabled for ServiceFeatureTable, GeodatabaseFeatureTable, and FeatureCollectionTable table types. They are disabled for all other table types and in the following circumstances:

• featureTable has a ServiceFeatureTable::featureRequestMode set to FeatureRequestMode::OnInteractionNoCache.
• featureTable is part of a FeatureLayer that sets FeatureLayer::tilingMode to FeatureTilingMode::Disabled. For feature fences from a ServiceFeatureTable, FeatureTilingMode::EnabledWithFullResolutionWhenSupported is recommended for highest accuracy.