About the Data Partition Action

The Data Partition Action works by mapping the fields from one data message to another. This is based upon the fields as defined in the source and destination dataset definitions. The source dataset definition is based upon the specific tracking service or connection that the action is associated with. The user then selects the destination dataset definition for the action. This may be the same, or different from, the source dataset definition.

Legacy:

Beginning with Tracking Server 10.1, automatic projection of real-time data will occur with a data partition action, if the spatial references of the source and target message definitions are different. In addition, automatic adjustment of data values in the time field will also occur if the source and target time zones are different.

It is important to note that, if the spatial reference and/or time zone of one of the message definitions changes after the data partition action is created, the action must be created again in order to project the real-time data and/or adjust the time values properly.

Once both the dataset definitions are known, then the mapping can be created. Field mapping is the assignment of a source field for a destination field. Each field in the destination can be assigned a source field. A destination field can also have no source—which means that it will create an empty field. In addition, two or more destination fields can be assigned the same source field. The following diagrams illustrate two possible field mappings.

Field mapping of two dissimilar dataset definitions.

Field mapping of the same dataset definition.

Note that the data types of the two columns mapped together sometimes must be identical, such as in the case of shapes, but can sometimes differ, such as in the case of integers and real numbers.