VMTI Video Moving Target Indicator
VSS VMTI Source Sensor
WA Wide Area
WAPS Wide Area Persistent Surveillance
3.2 UML notation
Most diagrams that appear in this standard are presented using the Unified Modeling Language UML static structure diagram, as described in Subclause 5.2 of [OGC 06-
121r3].
4 VMTI, GMTI and Tracking in the Context of OGC
4.1 Management Summary
This report provides an information model for the usage of video moving target indicator data VMTI, ground moving target indicator GMTI and tracking
information STANAG 4676 in the context of standardized spatial data infrastructures compliant to OGC and ISO standards.
It has been proven that all three specifications can get mapped to the OGC concept of operations using elements from the Geography Markup Language GML and
SweCommon, the data model and encoding defined by the Sensor Web Enablement suite of standards.
One issue is the definition of value ranges, which cannot be properly defined by XML Schema. XML Schema allows the definition of syntax patterns and enumeration
values, but does not support the definition of e.g. the dwell area range half extent to be withinthe interval 0 to 255.9928km. There are additional technologies providing
the required functionality available, e.g. Schematron.
The definition of bookmarks is partly covered by STANAG 4676, but requires further research. Currently, a single pointer with corresponding description field is all that is
available. The referenced resource remains undefined otherwise. The developed model in OWS8 serves as a first high-level approach but requires further
investigation. For additional further work items, please consult section 1.4.
All information models documented in this report have been serialized using XML Schema. The schemas are introduced in and bundled to OGC 11-108.
4.2 Introduction
This report provides an information model for the usage of video moving target indicator data VMTI, ground moving target indicator GMTI and tracking
information STANAG 4676 in the context of standardized spatial data infrastructures compliant to OGC and ISO standards. If possible, precedence shall be
given on using the OGC Sensor Web Enablement suite of standards, as this suite provides a homogeneous suite of standards to express sensor and sensor observation
data in the context of OGC. This means that all encodings shall be developed based on Observation and Measurements version 2 OM and implemented as an
application schema according to the rules of Geography Markup Language version 3.2 GML.
The mapping of GMTI, VMTI, and Track Model can be done following different OGC traditions by implementing it as a GML application schema using either base
GML types, using SweCommon as well as base GML types, or using SweCommon wherever possible. All three approaches shall be executed to test their applicability.
All target indicator and tracking data is provided in the form of Key-Length-Value encodings. KLV Key-Length-Value is a byte-level data-encoding standard used for
binary data byte-packing and metadata embedding into video feeds. Data is encoded into Key-Length-Value triplets, where Key identifies the data, Length specifies the
datas length, and Value is the data itself. It is defined in SMPTE 336M-2007 Data Encoding Protocol Using Key-Length Value, approved by the Society of Motion
Picture and Television Engineers. KLV encoding protocol defines a data structure, which is independent of the application or transportation method used. In contrast,
OGC preferred encodings make use of the extensible markup language XML. The goal of the work presented here was to develop a consistent conceptual mapping
between incoming KLV data and XML encoded data provided at OGC service endpoints. The implementation of the data conversion as well as synchronization
aspects between video or radar data with corresponding metadata was not subject of this work. A potential service portfolio to handle VMTI, GMTI and Tracking data is
documented in OGC Engineering Report 11-134.
5 Used Standards
5.1 MISB NATO
The following standards, engineering guidelines, and recommended practices form the base for this analysis:
Table 1: Overview of relevant standards
VMTI GMTI
Tracking
MISB STD 0601 NATO 4607 v3
NATO 4676 MISB RP 0903
NATO 4607 AEDP-8 Edition 1 Implementation Guide
Annex B to MISB RP 0903.2
NATO 4609
5.2 Observation and Measurement
The Observation Measurement OM specification defines a conceptual schema encoding for observations, and for features involved in sampling when making
observations. As a central part of the OGC SWE suite of standards, it is used by all service encodings to express observation data. OM is complemented by an XML
implementation that uses an automated framework to convert the strictly profiled