Actions and triggers

Extension ArcGIS Tracking Analyst provides a specialized mechanism for custom processing of tracking data. The custom processing is encapsulated in elements called actions, which are executed when the predefined conditions of a trigger are met. In Tracking Analyst, actions can be applied to tracking layers in a map document or they can be applied to real-time tracking services. If you are working with Esri Tracking Server, then actions can also be applied to tracking data at the server level.

Layer actions

Layer actions operate on features contained in a tracking layer. Therefore, they can be applied to both real-time and fixed-time tracking layers. Layer actions are saved in a map document and configured through the Actions tab on the Layer Properties dialog box. If you save a tracking layer as a layer file in ArcMap or ArcGlobe, its action settings are saved along with the layer.

Unlike service actions, layer actions exist entirely in the client application, such as ArcMap. Therefore, these actions are typically related to data visualization for analysis. For example, you can highlight features on the map that meet a certain trigger condition.

A highlight action is used to highlight hurricane events with high wind speed

Learn more about layer actions.

Service actions

Les actions de service s'appliquent aux messages de données lors de leur enregistrement en continu dans l'application cliente (ArcMap, par exemple) pour devenir des entités de suivi. Lorsque vous utilisez des données temps réel dans ArcGIS Tracking Analyst, les entités d'une couche de suivi en temps réel sont créées à partir des messages de données qui sont enregistrés en continu depuis un service de suivi. Par conséquent, les actions de service sont capables de modifier ou de supprimer les données contenues dans les messages de données de suivi avant leur transformation en entités.

Les actions de service sont définies pour un service de suivi, et non pour une couche. Elles ne peuvent donc pas être configurées par l'intermédiaire de la boîte de dialogue Propriétés de la couche. En revanche, elles doivent être configurées à l'aide de la boîte de dialogue Propriétés du service de suivi d'ArcCatalog ou de la fenêtre Catalogue d'ArcMap.

Learn more about service actions.

Triggers

Attribute triggers are used when you want an action to execute based on the values in certain data fields for an event. For example, if your tracking data contains a field for vehicle ID, you can trigger a highlight action only when the vehicle ID is equal to 2. This results in events for that vehicle being highlighted on the map.

Learn more about attribute triggers.

Location triggers are used to execute actions when certain spatial criteria are met. Location triggers can be used with any layer or service action. For example, you might want to highlight all events that are outside a particular boundary.

Location triggers require a set of polygon features to do a spatial comparison with. For layer actions, you must select a polygon layer. For service actions, you must select a polygon feature class. You can use location triggers independently to execute an action, or you can use them together with an attribute trigger.

Learn more about location triggers.

Defining multiple actions

Multiple actions can be defined for tracking layers and services. If you have more than one action defined, the ordering of your actions can become important. For example, filtering your data and then applying a highlight to the filtered data will likely give you a different result than applying the filter before the highlight. The order in which actions are evaluated can be configured on the Actions tab in the service or layer properties.