T.5.01.0

T.5.01.0 - GeoServices Event Notification

Overview

The GeoServices Event Notification transaction is published whenever GeoServices detects (or is informed) that a geo-spatial event (e.g. arrival, departure) has occurred for a given asset (or collection of connected assets). This event is only published if both the mobile asset and the landmark belong to the same division. Otherwise, the arrival/departure is considered superfluous.

Additionally, GeoServices may be optionally configured to publish updates to previous arrival/departure events. Specifically, these notifications are timestamp refinements that are published if the system learns that an asset actually arrived/departed from a landmark earlier than originally detected. For example, the system may first publish an 'arrival' notification that an asset arrived at a landmark at 10:00 PM. Later, it may learn that the asset actually arrived at 9:53 PM. If this case, the system will publish an 'arrival update'. Consumers of this notification must examine the gsEventID which will be one of the following:

• arrival
• departure
• arrival update
• departure update 

Note that some of the elements which may occur multiple times include:

• an <equipment> element is provided for each/every asset that may be connected
• a <proximity> element is provided for the closest city, the closest town, and the most relevant custom landmark that the asset(s) are at/nearby (if any)