About Tracking Services

The Tracking Services tab in Tracking Server Manager allows you to create, edit, and delete tracking services that are part of the Tracking Server Connector data link. You must first have message definitions in place before using them to create your tracking services.

When data messages enter as simple events, all of their attributes—including their geometry—are contained in the observation message definition. When they come in as complex events, their persistent information is contained in the object message definition. If your data messages contain complex events, you must choose both an observation and an object message definition.

Tip:

After editing a tracking service or its message definitions, you must disable and enable (checking off, then on) the Tracking Server Connector data link and click Save in order for the changes you have made to take effect.

Tracking Services

A tracking service can be composed of either a simple event or a complex event. A simple event uses a single message definition containing geographic feature information, temporal information, and other attribute information.

A complex event uses two message definitions: an observation message definition that provides temporal information and an object message definition that provides attribute information.

A complex event can join static tabular information to a real-time (dynamic) message in cases where the message contains the real-time position and the attribution is joined from a static source. For example, a moving vehicle position can be joined with static driver and model information.

Complex events can also combine real-time attributes with static geographic feature information. For example, real-time traffic sensor observations are joined with static geographic feature and attribute information.

Tracking services are created in Tracking Server Manager on the Tracking Services tab. Tracking services rely on message definitions that accurately describe the event data. If the message definition that the service is based on is removed from the server, the tracking service will also be deleted. A tracking service must be defined for event data to be available to the Tracking Server Connector data link.

A table containing simple events.

Two tables containing complex dynamic events.

Two tables containing complex stationary events.