GMTI Segments OGC GMTI Information Model

includes Target Reports for any GMTI detections observed within that dwell and shall be sent even if no targets are detected. The High Range Resolution HRR Segment provides data on HRR and Range-Doppler measurements, which may be performed in conjunction with MTI detections. It includes HRR Scatterer Data pertaining to the HRR measurements. The Job Definition Segment provides a definition of the radar job performed by the sensor, including information pertaining to the geolocation model used in the sensor measurement. The Free Text Segment provides a means of sending alphanumeric text messages. The Test and Status Segment provides a means of exchanging health and status information of the platform systems. The Processing History Segment provides a means of annotating the radar data to show its history as it is processed through various systems during transmission. The Platform Location Segment provides the means for the platform to transmit its location during periods when it is not collecting data. The Job Request and Job Acknowledge Segments are recommendations only and are not required for this format. The Job Request Segment provides a recommended format for requesting service from the sensor platform. The Job Acknowledge Segment provides a recommended format for acknowledging a sensor service request by a sensor platform, defining the job to be performed by the sensor, and notifying the requesting operator whether the task can be accomplished or not during the mission. The Group, Attached, LRI, and System-Specific Segments are undefined at this time and left for future definition.

8.3.2 GMTI Exploitation Classes

As there is no “predefined order or sequence other than the requirement to preface data segments with appropriate header segments”, raw GMTIF can hardly get directly converted into a hierarchical UMLXML model compliant to the OGC feature model approach. Instead, the GMTI data needs to get structured and organized to prepare it for further efficient processing. In this regard, we follow the recommendations provided in the STANAG 4607 implementation guide, which defines three exploitation classes: Situation Awareness SA: The minimum data required for Moving Target Indicator MTI target display. Targeting and Tracking TT: The minimum data required for targeting and tracking of MTI targets using current or advanced automatic tracking algorithms or precision location systems such as the Global Positioning System GPS. Targeting and Tracking with High Range Resolution HT: The minimum data required for targeting and tracking of MTI targets using current or advanced automatic tracking algorithms or precision location systems and High Range ResolutionRange-Doppler HRRR-D analysis of associated MTI targets

8.4 GMTI Observation Model

Each exploitation class is modeled as a specialization of OM_Observation. The following figure illustrates this mapping, which allows using GMTI data inline with the recommended practice of the STANAG 4607 implementation guide. The approach documented here makes use of different observation types. Alternatively, we could have modeled different result types, which are bound to a single GMTI observation type. The first approach was given precedence here, as it has the advantage that the mappings become more transparent and observation parsers can be better optimized for observation interpretation. Figure 19: UML model of GMTIObservation