[AIXM-496] Clearing equipment property for AirportClearanceService
ID: | AIXM-496 |
target version: | AIXM 5.2 |
version: | 1.0 |
last updated: | 24 JUN 2021 |
status: | PROPOSED |
Description
A new text attribute “clearingEquipment” is added in the AirportClearanceService feature type.
Rationale for change
See https://aixmccb.atlassian.net/browse/AIXM-421
The PANS-AIM, AD 2.7, line 1 requires the following information: "type(s) of clearing equipment". This information doesn’t exist in the AIXM 5.1 model, and would appear as a note in the ICAO AIP dataset.
Impact assessment
[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 new attribute to <feature> AirportClearanceService
- clearingEquipment, defined as “Type(s) of clearing equipment”, of type TextInstructionType.
The following UML diagram shows the new property:
Mapping AIXM 5.1.1 to AIXM 5.2 (forward)
Not applicable.
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 algorithm shall be applied:
- Remove the new “clearingEquipment” attribute Add an annotation.Note associated with the AirportClearanceService feature timeslice having
- purpose=“OTHER:BACKWARD_MAPPING”;
- translatedNote.LinguisticNote.note=”clearingEquipment: <clearingEquipment attribute value>”
Mapping example
(Note: for mapping test data see: https://github.com/aixm/mapping_52_511/tree/master/AIXM-xxx)
AIXM Input | AIXM Output |
---|---|
Backward Clearing equipement AirportClearanceService 5.2 input message:AIXMBasicMessage message:hasMember AirportHeliport gml:identifier = fac34bfc-fc4f-4da7-ad8a-84ee687f41bb timeSlice AirportHeliportTimeSlice 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 = designator = KEWR message:hasMember AirportClearanceService gml:identifier = fac34bfc-fc4f-4da7-ad8a-84ee687f41bc timeSlice AirportClearanceServiceTimeSlice 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 = airportHeliport = urn:uuid:fac34bfc-fc4f-4da7-ad8a-84ee687f41bb clearingEquipment = Runway Sweeper | Backward Clearing equipement AirportClearanceService 5.1.1 output message:AIXMBasicMessage message:hasMember AirportHeliport gml:identifier = fac34bfc-fc4f-4da7-ad8a-84ee687f41bb timeSlice AirportHeliportTimeSlice 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 = designator = KEWR message:hasMember AirportClearanceService gml:identifier = fac34bfc-fc4f-4da7-ad8a-84ee687f41bc timeSlice AirportClearanceServiceTimeSlice 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 = annotation Note purpose = OTHER:BACKWARD_MAPPING translatedNote LinguisticNote note = clearingEquipment: AirportClearanceService.clearingEquipment:Runway Sweeper airportHeliport = urn:uuid:fac34bfc-fc4f-4da7-ad8a-84ee687f41bb |