[AIXM-484] Rename RunwayVisualRange class
ID: | AIXM-484 |
target version: | AIXM 5.2 |
version: | 1.0 |
last updated: | 25 FEB 2021 |
status: | APPROVED |
Description
Rename the “RunwayVisualRange” class into "RunwayVisualRangeEquipment".
Rationale for change
See https://aixmccb.atlassian.net/browse/AIXM-349.
The current definition of the feature RunwayVisualRange (RVR) in AIXM is the following: “A meteorological equipment providing information about the distance over which the pilot of an aircraft on the centre line of a runway can see the runway surface markings of the lights delineating the runway or identifying its centre line.”
This definition does not align with the class name RunwayVisualRange due to its description as a meteorological equipment. In the ICAO ATM Information Reference Model (AIRM), there are both RunwayVisualRange and RunwayVisualRangeEquipment entities to represent the RVR measurements, as well as information on the equipment.
Therefore, the name of the AIXM feature "RunwayVisualRange" needs to be changed into "RunwayVisualRangeEquipment", to align with the definition of the feature and with its actual use in the model.
Impact assessment
[FWD_MAP_1:1] Data mapping is possible 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_1:1] Data mapping is possible and no data loss occurs 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:
- Rename <<feature>> “RunwayVisualRange” to “RunwayVisualRangeEquipment”.
Mapping AIXM 5.1.1 to AIXM 5.2 (forward)
[MAPC-00] The following algorithm shall be applied:
- For each RunwayVisualRange element:
- Rename RunwayVisualRange to RunwayVisualRangeEquipment
Mapping AIXM 5.2 to AIXM 5.1.1 (backward)
[MAPC-00] The following algorithm shall be applied:
- For each specified RunwayVisualRangeEquipment element:
- Rename RunwayVisualRangeEquipment to RunwayVisualRange.
Mapping example
(Note: for mapping test data see: https://github.com/aixm/mapping_52_511/tree/master/AIXM-xxx)
AIXM Input | AIXM Output |
---|---|
Backward RenameRVR RunwayVisualRange 5.2 input message:AIXMBasicMessage message:hasMember RunwayDirection gml:identifier = fac34bfc-fc4f-4da7-ad8a-84ee687f41bc timeSlice RunwayDirectionTimeSlice gml:validTime gml:TimePeriod gml:beginPosition = 2021-02-25 gml:endPosition = 2021-04-22 interpretation = PERMDELTA sequenceNumber = 1 featureLifetime gml:TimePeriod gml:beginPosition = 2009-01-01T00:00:00Z gml:endPosition = approachGuidance = PRECISION_CAT_II message:hasMember RunwayVisualRangeEquipment gml:identifier = fac34bfc-fc4f-4da7-ad8a-84ee687f41bb timeSlice RunwayVisualRangeEquipmentTimeSlice gml:validTime gml:TimePeriod gml:beginPosition = 2021-02-25 gml:endPosition = 2021-04-22 interpretation = PERMDELTA sequenceNumber = 1 featureLifetime gml:TimePeriod gml:beginPosition = 2009-01-01T00:00:00Z gml:endPosition = readingPosition = TDZ associatedRunwayDirection = urn:uuid:fac34bfc-fc4f-4da7-ad8a-84ee687f41bc | Backward RenameRVR RunwayVisualRange 5.1.1 output message:AIXMBasicMessage message:hasMember RunwayDirection gml:identifier = fac34bfc-fc4f-4da7-ad8a-84ee687f41bc timeSlice RunwayDirectionTimeSlice gml:validTime gml:TimePeriod gml:beginPosition = 2021-02-25 gml:endPosition = 2021-04-22 interpretation = BASELINE sequenceNumber = 1 featureLifetime gml:TimePeriod gml:beginPosition = 2009-01-01T00:00:00Z gml:endPosition = precisionApproachGuidance = ILS_PRECISION_CAT_II message:hasMember RunwayVisualRange gml:identifier = fac34bfc-fc4f-4da7-ad8a-84ee687f41bb timeSlice RunwayVisualRangeTimeSlice gml:validTime gml:TimePeriod gml:beginPosition = 2021-02-25 gml:endPosition = 2021-04-22 interpretation = BASELINE sequenceNumber = 1 featureLifetime gml:TimePeriod gml:beginPosition = 2009-01-01T00:00:00Z gml:endPosition = readingPosition = TDZ associatedRunwayDirection = urn:uuid:fac34bfc-fc4f-4da7-ad8a-84ee687f41bc |