ID:

AIXM-412

target version:

AIXM 5.2

version:

1.0

last updated:

10 MAY 2019

status:

APPROVED


Description

Add a new attribute to Airport Heliport to designate the time zone in which an airport/heliport is located and the eventual difference from the local time.

Rationale for change

See https://aixmccb.atlassian.net/browse/AIXM-345

The AirportHeliport element in AIXM does not capture the time zone in which an airport/heliport is located. This information can be found in chart supplements in order to allow pilots and international users to determine the local time for operating hours, service availability, and local NOTAM applicability using the provided UTC time. 

Due to its operational usage, a time zone attribute should be added to AirportHeliport in AIXM, with the CodeTimeReferenceType as the associated code list containing the UTC time zones.  Additionally, coded values will be added into the CodeTimeReferenceType to account for airports in time zones that do not fall directly on the hour.

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: 

  • In the AirportHeliport feature:
    • Add a new timeZone attribute defined as “The indication of the time reference system in which an airport/heliport resides”, data type CodeTimeReferenceType
  • In the CodeTimeReferenceType data type:
    • Add new coded values:
      • UTC-9:30: UTC minus 9 hours and 30 minutes
      • UTC-3:30: UTC minus 3 hours and 30 minutes
      • UTC-2:30: UTC minus 2 hours and 30 minutes
      • UTC+4:30: UTC plus 4 hours and 30 minutes
      • UTC+5:30: UTC plus 5 hours and 30 minutes
      • UTC+5:45: UTC plus 5 hours and 45 minutes
      • UTC+6:30: UTC plus 6 hours and 30 minutes
      • UTC+8:45: UTC plus 8 hours and 45 minutes
      • UTC:+9:30: UTC plus 9 hours and 30 minutes
      • UTC+10:30: UTC plus 10 hours and 30 minutes
      • UTC+12:45: UTC plus 12 hours and 45 minutes


The UML class diagram shows the main new elements of the new model for time zone.

Mapping AIXM 5.1.1 to AIXM 5.2 (forward)

[MAPC-01]The forward mapping approach proposed in this case is as follows:

  • Replace “OTHER:MINUS_2H30” with “-2:30”
  • Replace “OTHER:MINUS_3H30” with “-3:30”
  • Replace “OTHER:MINUS_9H30” with “-9:30”
  • Replace “OTHER:PLUS_10H30” with “+10:30”
  • Replace “OTHER:PLUS_12H45” with “+12:45”
  • Replace “OTHER:PLUS_4H30” with “+4:30”
  • Replace “OTHER:PLUS_5H30” with “+5:30”
  • Replace “OTHER:PLUS_5H45” with “+5:45”
  • Replace “OTHER:PLUS_6H30” with “+6:30”
  • Replace “OTHER:PLUS_8H45” with “+8:45”
  • Replace “OTHER:PLUS_9H30” with “+9:30”

Mapping AIXM 5.2 to AIXM 5.1.1 (backward)

[MAPC-01]The backward mapping approach proposed in this case is as follows:

  • Replace “-2:30” with “OTHER:MINUS_2H30” 
  • Replace “-3:30” with “OTHER:MINUS_3H30” 
  • Replace “-9:30” with “OTHER:MINUS_9H30” 
  • Replace “+10:30” with “OTHER:PLUS_10H30” 
  • Replace “+12:45” with “OTHER:PLUS_12H45”
  • Replace “+4:30” with “OTHER:PLUS_4H30”
  • Replace “+5:30” with “OTHER:PLUS_5H30”
  • Replace “+5:45” with “OTHER:PLUS_5H45”
  • Replace “+6:30” with “OTHER:PLUS_6H30”
  • Replace “+8:45” with “OTHER:PLUS_8H45”
  • Replace “+9:30” with “OTHER:PLUS_9H30”

Mapping example

Mapping example to be added...


(Note: for mapping test data see: https://github.com/aixm/mapping_52_511/tree/master/AIXM-xxx

AIXM 5.2AIXM 5.1(.1)
  ...





...



  • No labels