Supported with:
- Engine with Tracking
- ArcView with Tracking Analyst
- ArcEditor with Tracking Analyst
- ArcInfo with Tracking Analyst
- Server with Tracking
Library dependencies: System, SystemUI, Geometry, Display, Server, Output, Geodatabase, GISClient, ArcWeb, DataSourcesFile, DataSourcesGDB, DataSourcesOleDB, DataSourcesRaster, DataSourcesNetCDF, GeoDatabaseDistributed, GeoDatabaseExtensions, Carto, NetworkAnalysis, Location, GeoAnalyst, Animation, Maplex, Geoprocessing, NetworkAnalyst, Schematic, SpatialAnalyst, 3DAnalyst, GlobeCore, PublisherAdditional 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 within ArcGIS.
Developers do not extend this library.
The objects that implement this functionality are grouped into a number of library subsystems. These library subsystems are:Tracking Analyst extension
The Tracking Analyst extension glues all of 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 views 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 in order 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:
-
Common Temporal Reference—Provides a single temporal perspective for all display objects within Tracking Analyst. When analyzing data from different sources, it's important to synchronize the data's temporal reference so the state of the data shares common references, such as a common spatial extent and a common temporal perspective in time. This feature provides the mechanism to allow the temporal objects to efficiently archive this common reference.
-
Dynamic Display Manager—Provides a mechanism to automatically update the display at a configured interval and provides methods to allow other software components to request animation updates to the display in a synchronized manner.
-
Tracking Label Engine—The display of dynamic labels on top of temporal-based objects requires the introduction of a special label engine. This label engine provides the capability to efficiently label features on the screen that change dynamically over time.
Temporal presentation
The temporal presentation subsystem contains objects that display time series data in a map.
This subsystem is composed of the following:
-
Temporal Feature Layer—Based on the feature layer with extensions that enable the display of time series data. This layer will temporally index standard ESRI feature classes that contain date and time data as one of their attributes and display this time series feature class data in temporal order. This layer introduces capabilities to query such data for a given temporal extent and to temporally offset such data.
-
Temporal Legend Objects—Provides capabilities to symbolize data based on temporal offsets from the current temporal perspective. These objects are based on ESRI's legend objects and extend these objects to provide storage and temporal analysis of time data to determine what temporal symbology to use.
-
Temporal Renderer—Provides a container that allows you to configure the temporal layer to symbolize time series data using temporal modifications to standard ESRI event-based rendering. Temporal symbolization options include filter data, symbolizing data, size a symbol, or color a symbol based on time from a reference time.
Tracking data catalog
The tracking data catalog support subsystem implements a light-weight cataloging set of objects that are only 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.
- Highlight specific features
- Temporal Legend Objects
- Temporal Renderer
Tracking utility
The tracking utility subsystem is a general-purpose area for components that serve utility functions. The most notable utility is the GML converter utility object. This object converts simple point, line, or polygon geometries to XML format using the GML specification as well as reconstituting geometry from a GML XML document.
The following sample demonstrates the use of the GMLConverter component to convert point geometry to a GML string.
[C#]
private string ConvertGeomToGML()
{
IGMLConversion pGMLConversion = new GMLConverterClass();
IPoint piPoint = new PointClass();
piPoint.PutCoords(55, 99);
pGMLConversion.ESRIGeometry = piPoint;
string strGML = pGMLConversion.GML;
return strGML;
}
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 four message components referred to as message types: data, command, status, and command responses. Each of the four message types share or implement the
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 to 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 either 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).
