Figure 28: UML model of SituationAwarenessObservation
The specialized observation type overrides the result element only. Each target is described in a SituationAwarenessTargetReport. There can be any number of
SituationAwarenessTargetReports in the result element.
Figure 29: UML model of SituationAwarenessTargetReport
The SituationAwarenessTargetReportdefines the location of the target either using the North-South position of the reported detection, expressed as degrees North positive
or South negative from the Dwell Area Center Latitude the Reference Point, and the East-West position of the reported detection, expressed as degrees East positive
from the Dwell Area Center Longitude the Reference Point, or in form of a GM_Point, which describes the absolute position of the target.
8.6 Targeting and Tracking Observation
TheTargetingAndTrackingObservation provides 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.
Figure 30: UML model of TargetingAndTrackingObservation
The specialized observation type overrides the result element only. Each target is described in a TargetingAndTrackingReport. There can be any number of
TargetingAndTrackingReports in the result element. The TargetingAndTrackingReport is derived from the SituationAwarenessTargetReport
and therefore inherits all elements contained therein. It contains all GMTI elements recommended by the 4607 implementation guide. Additional elements are provided in
4607v3 and might get added additionally.
Figure 31: UML model of TargetingAndTrackingReport
The TargetingAndTrackingReport makes use of the swe:Quantity elements to map all simple data types. The Target Classification is mapped to the enumeration
TargetClassification.
Figure 32: UML model of TargetClassification
8.7 Target and Tracking HRR Observation
The TargetingAndTrackingHRRObservation provides 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.
The GMTI field Existence Mask field has become superfluous, as this five-byte field that immediately follows the Segment Header fields is used to identify the existence
of each field of the HRR Segment, with the exception of the Existence Mask itself, by a reserved bit.
Figure 33: UML model of TargetingAndTrackingHRRObservation
The specialized observation type overrides the result element only. Each target is described in a TargetingAndTrackingHRRReport. There can be any number of
TargetingAndTrackingHRRReports in the result element. The TargetingAndTrackingHRRReport is derived from the TargetingAndTrackingReport
and therefore inherits all elements contained therein. It contains all GMTI elements recommended by the 4607 implementation guide. Additional elements are provided in
4607v3 and might get added additionally.
