Supported with:
Library dependencies: System, SystemUI, Geometry, Display, Server, Output, Geodatabase, GISClient, DataSourcesFile, DataSourcesGDB, DataSourcesOleDB, DataSourcesRaster, DataSourcesNetCDF, GeoDatabaseDistributed, GeoDatabaseExtensions, Carto, NetworkAnalysis, Location, GeoAnalyst, Animation, Maplex, Geoprocessing, NetworkAnalyst, Schematic, SpatialAnalyst, 3DAnalyst, GlobeCore

Additional library information: Contents, Object Model Diagram

The TrackingAnalyst library implements the non-user interface functionality of the Tracking Analyst extension to ArcMap. The Tracking Analyst extension supports the display, analysis, and manipulation of temporal data in ArcGIS.
Developers do not extend this library.

See the following sections for more information about this namespace:

Tracking Analyst extension

The Tracking Analyst extension binds the temporal and tracking components of Tracking Analyst into a cohesive set of objects that collectively allows for the display and analysis of temporal data. Tracking Analyst considers temporal data as a series of observations over time that have attribute and spatial importance. The extension provides the framework from which the temporal-based objects are attached to provide synchronized time across many tracking layers. This framework also provides the dynamic display management required to keep the display synchronized with the user-defined temporal perspective. A temporal perspective is either the current system time or a point in time of your choosing.
This subsystem manages the following functional aspects of Tracking Analyst:

Temporal presentation

The temporal presentation subsystem contains objects that display time series data in a map.
This subsystem is composed of the following:

Tracking data catalog

The tracking data catalog support subsystem implements a light-weight cataloging set of objects that are dependent on the ArcGIS Engine component libraries. This enables data catalog capabilities without using the ArcGIS application component libraries.

Action processor

The action processor subsystem provides a processing engine and action objects that allow for the dynamic analysis of streaming or display data. This subsystem is consumed by the tracking presentation and tracking data source. Each consumer of the action processing subsystem utilizes its capabilities for a specific purpose. The tracking presentation subsystem uses this subsystem while rendering symbology. See the following:

Tracking utility

The tracking utility subsystem is a general purpose area for components that serve utility functions. The most notable utility is the Geography Markup Language (GML) converter utility object. This object converts simple point, line, or polygon geometries to Extensible Markup Language (XML) format using the GML specification, as well as reconstituting geometry from a GML XML document.
The following code example shows the use of the GMLConverter component to convert point geometry to a GML string:
Point point = new Point();
GMLConverter converter = new GMLConverter();
point.putCoords(55, 99);
String GML = converter.getGML();
System.out.println("GML output: " + GML);

Tracking messages

The message system is the common framework by which messages are transmitted and received in the tracking data source. The message system is composed of the following message components referred to as message types:
Each of the message types share or implement the esriTrackingAnalyst.IMessage interface. This interface provides a base set of functionality that enables the tracking data source to handle, route, or broadcast any of the message types without regard for their type.

Tracking data

The tracking data source subsystem contains a geodatabase implementation for real-time data. This subsystem is composed of the traditional geodatabase constructs, such as workspacefactory, workspace, and feature class. It also introduces the construct of a data source connection. This connection provides a list of tracking services and tracking data definitions.
A tracking service can be simple or complex. The simple data service provides one data event that describes the time series events containing the time, attribute, and spatial information. The complex data service provides two data events that describe the time series as a composite of two events containing the time, attribute, and spatial information. The current implementation of this data source does not provide editing capability through the application programming interface (API).