14 MAY 2019
Add new attributes to VisualGlideSlopeIndicator feature to designate the distance from the runway threshold and the angle of displacement from the runway centreline.
Rationale for change
The VisualGlideSlopeIndicator feature in the current AIXM 5.1.1 model does not have the ability to designate the distance from the Visual Glide Slope Indicator (VGSI) Runway Reference Point (RRP) to the runway threshold or displaced runway threshold (when applicable). The RRP is the point where the VGSI angle of visual approach intercepts the runway centerline on the runway surface. The RRP is required for flight inspections of VGSI and therefore warrants introduction into AIXM v5.2.
Additionally, in AIXM 5.1.1 it is not possible to identify the angle of displacement of the axis of a VGSI relative to the runway centreline. The angle of displacement from the centreline is identified in ICAO Annex 14 (Aerodromes) as information to be made available, and therefore this information is proposed to be added into AIXM v5.2.
[FWD_1:1] No data mapping is necessary and no data loss occurs when data is exchanged from a system (A) that uses AIXM 5.1.1 for output towards a system (B) that uses AIXM 5.2 for input.
[BWD_MAP_LOSS] Data mapping is possible, but some data would be lost (or converted into Notes) when data is exchanged from a system (B) that uses AIXM 5.2 for output towards a system (A) that uses AIXM 5.1.1 for input.
Change Proposal details
In the UML model, add the following attributes to the VisualGlideSlopeIndicator feature:
- thresholdDistance: (data type: ValDistanceType; definition: The distance from the runway reference point (RRP) to the runway threshold.
- displacementAngle: (data type: ValAngleType; definition: The angle of displacement of the axis of the VGSI relative to the runway centreline.)
The UML class diagram highlights the new attributes.
Mapping AIXM 5.1.1 to AIXM 5.2 (forward)
Mapping AIXM 5.2 to AIXM 5.1.1 (backward)
[MAPC-02] From the three backward mapping options applicable in this case, the first two (discard the value or use an extension) are straightforward and do not need any further details. The 3rd option (backward mapping into a Note) is detailed in order to provide a complete description of this case and its conversion option. The following mapping into Note algorithm is proposed:
For each VisualGlideSlopeIndicator that has a specified thresholdDistance:
- Remove the thresholdDistance
- Add an annotation.Note associated with the VisualGlideSlopeIndicator class having
- translatedNote.LinguisticNote.note=”thresholdDistance: <thresholdDistance> <uom>”;
- propertyName = “position”
For each VisualGlideSlopeIndicator that has a specified displacementAngle:
- Remove the displacementAngle
- Add an annotation.Note associated with the VisualGlideSlopeIndicator class having:
- translatedNote.LinguisticNote.note=”displacementAngle: <displacementAngle>”;
- propertyName = “position”
Mapping example to be added...
(Note: for mapping test data see:)
|AIXM 5.2||AIXM 5.1(.1)|