target version:

AIXM 5.2



last updated:

15 MAY 2019




Add a new attribute to allow for the designation of an airport having an associated segmented circle marker.

Rationale for change


AIXM does not capture whether an airport has an associated segmented circle marker.   The segmented circle performs two functions - it aids the pilot in locating airports and it provides a centralized location for such indicators and signal devices as may be required on a particular airport.  Segmentation of the circle is necessary so that it can be distinguished from a solid circle which can sometimes be used to mark the center of a landing area. 

The presence of  segmented circle marker systems will be added into the AirportHeliport feature as an attribute.

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_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:

  • In the AirportHeliport feature
  • Add a new segmentedCircleMarker attribute, defined as “the indication of the presence of a segmented circle marker system at an airport/heliport”, data type CodeSegmentedCircleBaseType
  • Add a new data type CodeSegmentedCirlceBaseType  defined as “a code indicating the availability of segmented circle markers”:
  • Add new coded values:
    • NO: Segmented circle marker is not available
    • YES: Segmented circle marker is available
    • YES_LIGHTED: Lighted segmented circle marker is available
    • OTHER: Other
  • Add a new data type CodeSegmentedCircleType (specialisation of CodeSegmentedCircleBaseType, stereotype <<datatype>>, definition: “A complex data type that enables the provision of a NIL reason for any attribute using this type”) attribute:
    • nilReason (type: NilReasonEnumeration)

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 mapping into Note algorithm is proposed:

  • Remove the new element
  • Add an annotation.Note associated with the owner class having
    • translatedNote.LinguisticNote.note=”segmentedCircleMarker:<CodeSegmentedCircleType>

Mapping example

Mapping example to be added...

(Note: for mapping test data see:

AIXM 5.2AIXM 5.1(.1)


  • No labels