For more information, refer to ICAO Data Sets Coding Guidelines in AIXM 5.1/5.1.1 format on aixm.aero.
The coding guidelines have been initially developed by EUROCONTROL and further maintained by the AIXM Community.
| Subject | Property | Sub-Property | ID | Type | Description | Note | Reference | AIXM5.1(1) | Remarks |
|---|---|---|---|---|---|---|---|---|---|
| ATS-Route | Designator | 432 | Text | Designators for ATS routes according to Annex 11 Appendix 1 (or Appendix 3 for standard departure and arrival routes) | Doc 10066 App 2 AIP ENR 3.1.1, ENR 3.3.1; Annex 11 2.12, App 1, App 3; Annex 4 7.9.3.1.1 | //aixm:Route//aixm:designatorPrefix| //aixm:Route//aixm:designatorSecondLetter | //aixm:Route//aixm:designatorNumber | //aixm:RouteSegment//aixm:designatorSuffix | //aixm:Route//aixm:multipleIdentifier | The RouteSegment.designatorSuffix has been added, as in some countries a route may have a different designator suffix for particular route segments. | ||
| Route segment | From point | Designator | 460 | Text | The coded designators or name-codes of significant point | Doc 10066 App 2 AIP ENR 3.1.1, ENR 3.3.1, ENR 4.4.3; Annex 4 7.9.3.1.1 | //aixm:RouteSegment//aixm:start/aixm:EnRouteSegmentPoint/aixm:pointChoice_navaidSystem OR //aixm:RouteSegment//aixm:start/aixm:EnRouteSegmentPoint/aixm:pointChoice_fixDesignatedPoint OR //aixm:RouteSegment//aixm:start/aixm:EnRouteSegmentPoint/aixm:pointChoice_airportReferencePoint | Although via pointChoice selectable as SignificantPoint for the RouteSegment.start the assumption is made that RunwayCentrelinePoint, TouchDownLiftOff and Point may not be used for that purpose. A corresponding coding/verification rule may be established. | |
| Reporting | 461 | Code list | Indication of ATS / MET reporting requirement “compulsory” or “on-request” | Doc 10066 App 2 AIP ENR 3.1.1, ENR 3.3.1, ENR 4.4.3; Annex 4 7.9.3.1.1 | //aixm:RouteSegment//aixm:start/aixm:EnRouteSegmentPoint/aixm:reportingATC | ||||
| To point | Reporting | 463 | Code list | Indication of the ATS / MET reporting requirement “compulsory” or “on-request” | Doc 10066 App 2 AIP ENR 3.1.1, ENR 3.3.1, ENR 4.4.3; Annex 4 7.9.3.1.1 | //aixm:RouteSegment//aixm:end/aixm:EnRouteSegmentPoint/aixm:reportingATC | |||
| Designator | 462 | Text | The coded designators or name-codes of significant point | Doc 10066 App 2 AIP ENR 3.1.1, ENR 3.3.1, ENR 4.4.3; Annex 4 7.9.3.1.1 | //aixm:RouteSegment//aixm:end/aixm:EnRouteSegmentPoint/aixm:pointChoice_navaidSystem OR //aixm:RouteSegment//aixm:end/aixm:EnRouteSegmentPoint/aixm:pointChoice_fixDesignatedPoint OR //aixm:RouteSegment//aixm:end/aixm:EnRouteSegmentPoint/aixm:pointChoice_airportReferencePoint | Although via pointChoice selectable as SignificantPoint for the RouteSegment.start the assumption is made that RunwayCentrelinePoint, TouchDownLiftOff and Point may not be used for that purpose. A corresponding coding/verification rule may be established. | |||
| Track | 438 | Bearing | Track, VOR radial or magnetic bearing of a route segment | Doc 10066 App 2 AIP ENR 3.1.2, ENR 3.3.3; Annex 4 7.9.3.1.1; Annex 11 App 5 Table 4 | //aixm:RouteSegment//aixm:trueTrack | //aixm:RouteSegment//aixm:reverseTrueTrack | //aixm:RouteSegment//aixm:magneticTrack | //aixm:RouteSegment/aixm:reverseMagneticTrack | ||||
| Changeover point | 439 | Point | The point at which an aircraft navigating on an ATS route segment defined by reference to very high frequency omnidirectional radio ranges is expected to transfer its primary navigational reference from the facility behind the aircraft to the next facility ahead of the aircraft. | in case of VOR radial | Doc 10066 App 2 AIP ENR 3.1.2 | //aixm:ChangeOverPoint | In AIXM the ChangeOverPoint does not reference a RouteSegment but a RoutePortion. A RoutePortion starts and ends at a SignificantPoint. In order to relate a Change Over Point to a Route Portion, the Route Portion concerned has also to be defined in the AIP data set. In PANS-AIM required for ENR 3.1, 3.2 & 3.4 in case of VOR radials | ||
| Length | 440 | Distance | The geodesic distance between from point and to point | Airway segments length \nTerminal arrival or departure route segments length | Doc 10066 App 2 AIP ENR 3.1.2, ENR 3.3.3; Annex 4 7.9.3.1.1; Annex 11 App 5 Table 5 | //aixm:RouteSegment//aixm:length | //aixm:RouteSegment//aixm:pathType | //aixm:RouteSegment//aixm:annotation//aixm:Note[aixm:propertyName=length] | In order to know if the distance provided is geodesic (or e.g. gerat circle) the attribute pathType should be coded. AIXM 5.1.1 does not have a dedicated attribute for accuracy. A corresponding Note may be coded. | ||
| Upper limit | 441 | Altitude | The upper limit of the route segment | Doc 10066 App 2 AIP ENR 3.1.3, ENR 3.3.4; Annex 4 7.9.3.1.1 | //aixm:RouteSegment//aixm:upperLimit | //aixm:RouteSegment//aixm:upperLimitReference | ||||
| Lower limit | 442 | Altitude | The lower limit of the route segment | Doc 10066 App 2 AIP ENR 3.1.3, ENR 3.3.4; Annex 4 7.9.3.1.1 | //aixm:RouteSegment//aixm:lowerLimit | //aixm:RouteSegment//aixm:lowerLimitReference | ||||
| MEA | 443 | Altitude | Minimum en-route altitude (MEA). The altitude for an en-route segment that provides adequate reception of relevant navigation facilities and ATS communications, complies with the airspace structure and provides the required obstacle clearance. | Doc 10066 App 2 AIP ENR 3.1.3; Annex 4 7.9.3.1.1; Doc 8168 Vol 2 Part II, Section 3 1.6.1; Annex 11 2.22, App 5 | //aixm:RouteSegment//aixm:minimumEnrouteAltitude | //aixm:RouteSegment//aixm:annotation//aixm:Note[aixm:propertyName=minimumEnrouteAltitude] | In PANS-AIM listed in chapter 5.3.3.1.1 but only required in ENR 3.1. PANS-AIM requires a accuracy to be specified for the MEA. AIXM does not have a dedicated attribute for that purpose. A Note may be coded. | |||
| MOCA | 444 | Altitude | Minimum obstacle clearance altitude (MOCA). The minimum altitude for a defined segment of flight that provides the required obstacle clearance. | Doc 10066 App 2 AIP ENR 3.1 4, Doc 8168 Vol 2 Part II Section 3 1.6.1; Annex 11 2.22, App 5 | //aixm:RouteSegment//aixm:minimumObstacleClearanceAltitude | //aixm:RouteSegment//aixm:annotation//aixm:Note[aixm:propertyName=minimumEnrouteAltitude] | In PANS-AIM listed in 5.3.3.1 but only required in ENR 3.1. PANS-AIM requires a accuracy to be specified for the MOCA. AIXM does not have a dedicated attribute for that purpose. A Note may be coded. | |||
| Minimum flight altitude | 445 | Altitude | Minimum flight altitude | Doc 10066 App 2 AIP ENR 3.4.4; Annex 11 2.22, App 5 | //aixm:RouteSegment//aixm:minimumObstacleClearanceAltitude | //aixm:RouteSegment//aixm:annotation//aixm:Note[aixm:propertyName=minimumObstacleClearanceAltitude] | OR //aixm:RouteSegment//aixm:minimumEnrouteAltitude | //aixm:RouteSegment//aixm:annotation//aixm:Note[aixm:propertyName=minimumEnrouteAltitude] | In PANS-AIM required only for ENR 3.4 Helicopter routes. AIXM does not have a dedicated attribute for that purpose. For this mapping it is assumed that it may be the either the MEA or the MOCA for helicopters. PANS-AIM requires a accuracy to be specified for the Minimum flight altitude. AIXM does not have a dedicated attribute for that purpose. A Note may be coded. | |||
| Lateral Limits | 446 | Distance | Lateral limits of route | Doc 10066 App 2 AIP ENR 3.1.4 | //aixm:RouteSegment//aixm:widthLeft | //aixm:RouteSegment//aixm:widthRight | ||||
| Restrictions | 449 | Text | Indication on any area speed and level/altitude restrictions where established; | Doc 10066 App 2 AIP ENR 3.1.7, AIP ENR 3.3.7; Annex 4 8.9.4, 7.9.3.1.1 | |||||
| Direction of cruise levels | Backward | 452 | Code list | Indication on the direction of the cruising level (even, odd, NIL) from second point to first point of route segment | Doc 10066 App 2 AIP ENR 3.1.5, AIP ENR 3.3.5, Annex 4 7.9.3.1.1 | //aixm:RouteSegment//aixm:availability/aixm:RouteAvailability[aixm:direction=BACKWARD]/aixm:levels/aixm:AirspaceLayer/aixm:discreteLevelSeries | |||
| Forward | 451 | Code list | Indication on the direction of the cruising level (even, odd, NIL) from first point to second point of route segment | Doc 10066 App 2 AIP ENR 3.1.5, AIP ENR 3.3.5, Annex 4 7.9.3.1.1 | //aixm:RouteSegment//aixm:availability/aixm:RouteAvailability[aixm:direction=FORWARD]/aixm:levels/aixm:AirspaceLayer/aixm:discreteLevelSeries | ||||
| Availability | 456 | Text | Information on the route availability | Doc 10066 App 2 AIP ENR 3.1.7, AIP ENR 3.3.7; Annex 4 7.9.3.1.1 | |||||
| Class of airspace | 457 | Text | Classification of airspace (A, B, … G) which determines the operating rules, flight requirements, and services provided. According to Annex 11, Appendix 4 | Doc 10066 App 2 AIP ENR 3.1.3, AIP ENR 3.3.4 | N/A | In PANS-AIM required for ENR 3.1, 3.2, 3.3 & 3.4 In AIXM 5.1(.1) there is no dedicated attribute for class of airspace for the RouteSegment. The class of airspace has to be derived (by a system) from the Airspace the Route segment is located in. A CP was created to provide a corresponding attribute; see CCB AIXM-183 | |||
| PBN requirements | Sensor requirements | 465 | Text | Indication on the sensor requirements including any navigation specification limitations | PBN only | Doc 10066 App 2 AIP ENR 3.1, ENR 3.4 | |||
| Navigation performance requirements | 464 | Text | The navigation accuracy requirement for each PBN (RNAV or RNP) route segment | PBN only | Doc 10066 App 2, AIP ENR 3.1.6, AIP ENR 3.3.6 | //aixm:RouteSegment//aixm:requiredNavigationPerformance | In PANS-AIM required only for ENR 3.3 Area navigation routes. AIXM 5.1(.1) issue The data type for requiredNavigationPerformance, the codeRNPType does not seem to be properly defined in AIXM 5.1(.1). It is not a codelist, and does not have a pattern neither, it is just a string. The AIXM term requiredNavigationPerformance may lead to the assumption that only RNP values may be coded but no RNAV values (e,g. RNP 4 but not RNAV 5). | ||
| Navigation specification | 435 | Text | Designation of the navigation specification(s) applicable to a specified segment(s) - There are two kinds of navigation specifications:\nRequired navigation performance (RNP) specification. A navigation specification based on area navigation that includes the requirement for performance monitoring and alerting, designated by the prefix RNP, e.g. RNP 4, RNP APCH.\nArea navigation (RNAV) specification. A navigation specification based on area navigation that does not include the requirement for performance monitoring and alerting, designated by the prefix RNAV, e.g. RNAV 5, RNAV 1. | PBN only | Doc 10066 App 2 AIP ENR 3.1.1, AIP ENR 3.3.1; Annex 4 7.9.3.1.1 | //aixm:RouteSegment//aixm:navigationType | The navigationType attribute of AIXM only provides as values RNAV, CONV and TACAN., but no PBN specifications (such as RNAV 10 , RNP 4 etc) Workaround for AIXM5.1(.1): Use OTHER to code the Navigation specification , e.g. OTHER:RNAV_10 or OTHER:RNP_4, etc. Status: for AIXM 5.2 see CCB AIXM-135 | ||
| Controlling unit | Name | 466 | Text | Name of the unit providing the service | Doc 10066 App 2 AIP ENR 3.1.7, ENR 3.3.7 | //aixm:Unit//aixm:name | |||
| Channel | 467 | Text | Operating channel / frequency of controlling unit | Doc 10066 App 2 AIP ENR 3.1.7, ENR 3.3.7 | //aixm:AirTrafficControlService//aixm:radioCommunication OR //aixm:SearchRescueService//aixm:radioCommunication OR //aixm:InformationService//aixm:radioCommunication AND //aixm:RadioCommunicationChannel//aixm:frequencyTransmission | //aixm:RadioCommunicationChannel//aixm:frequencyReception | //aixm:RadioCommunicationChannel//aixm:channel | ||||
| Logon address | 468 | Text | A specified code used for data link logon to the controlling ATS unit | if applicable | Doc 10066 App 2 AIP ENR 3.1.7, ENR 3.3.7 | TBD | There are several options to encode datalink information in AIXM 5. For TrafficSeperationService two dedicated attributes are provided: dataLinkEnable and dataLinkChannel. For InformationService only one attribute dataLink is provided. In addtion it is possible to encode datalink information for an Unit via the object OnlineContact using the attributes linkage, network and protocol. | ||
| Other route | Designator | 992 | Text | Designator of the route | Doc 10066 App 2 AIP ENR 3.5 | //aixm:Route//aixm:designatorPrefix| //aixm:Route//aixm:designatorSecondLetter | //aixm:Route//aixm:designatorNumber | //aixm:RouteSegment//aixm:designatorSuffix | //aixm:Route//aixm:multipleIdentifier | The RouteSegment.designatorSuffix has been added, as in some countries a route may have a different designator suffix for particular route segments. | ||
| Type | 993 | Text | Type of route (e.g. VFR uncontrolled navigation routes) | Doc 10066 App 2 AIP ENR 3.5 | |||||
| Flight rules | 994 | Code list | Information on the flight rules that apply on the route (IFR / VFR) | Doc 10066 App 2 AIP ENR 3.5 | //aixm:Route//aixm:flightRules | Acc. to PANS-AIM only relevant for Other routes. It is probably assumed that ATS routes are for IFR and other routes include both IFR and VFR routes. | |||
| Waypoint | Identification | 470 | Text | Names, coded designators or name-codes assigned to the significant point. | Doc 10066 App 2 AIP ENR 4.4.1, Annex 4 7.9.3.1.1, Annex 11 App 2 2,3 | //aixm:DesignatedPoint//aixm:designator | //aixm:DesignatedPoint//aixm:name | In AIXM, there is a dedicated attribute for designator and another one for name. As according to PANS-AIM a designated point may be identified either by a name or a designator, both attributes are mapped. In case a designated point has only a name, it is assumed that certain naming conventions will be applied (e.g. defined in ARINC 424) in order to construct a corresponding designator. | ||
| Position | 473 | Point | Geographical location of the waypoint | Doc 10066 App 2 AIP ENR 4.4.2, Annex 4 7.9.3.1.1, Annex 11 App 5 Table 1 | //aixm:DesignatedPoint//aixm:location | //aixm:DesignatedPoint//aixm:location//aixm:horizontalAccuracy | ||||
| Formation | Distance | 478 | Distance | The distance from the reference VOR/DME, if the waypoint is not collocated with it; | Distance used for the formation of an en-route fix | Doc 10066 App 2 AIP ENR 3.3.2, Annex 11 App 5 Table 5 | //aixm:DistanceIndication/aixm:distance | //aixm:DistanceIndication/aixm:fix/aixm:DesigantedPoint | //aixm:DistanceIndication//aixm:annotation//aixm:Note[aixm:propertyName=distance] | PANS-AIM requires an Accuracy for the Formation - Distance. AIXM 5.1.1 does not provide a dedicated attribute. Note may be used to code that information. | |
| Navaid | 476 | Text | The station identification of the reference VOR/DME | Doc 10066 App 2 AIP ENR 3.3.2 | //aixm:AngleIndication//aixm:pointChoice_navaidSystem | //aixm:DistanceIndication//aixm:pointChoice_navaidSystem | ||||
| Bearing | 477 | Bearing | The bearing from the reference VOR/DME, if the waypoint is not collocated with it; | Bearing used for the formation of an en-route fix | Doc 10066 App 2 AIP ENR 3.3.2, Annex 11 App 5 Table 4 | //aixm:AngleIndication//aixm:angle | //aixm:AngleIndication//*[aixm:indicationDirection=FROM] | //aixm:AngleIndication//aixm:fix/aixm:DesignatedPoint //aixm:AngleIndication//aixm:annotation//aixm:Note[aixm:propertyName=angle] | PANS-AIM requires an Accuracy for the Formation - Bearing. AIXM 5.1.1 does not provide a dedicated attribute. Note may be used to code that information. | ||
| En-route Holding | Identification | 480 | Text | Identification of the holding procedure | Doc 10066 App 2 AIP ENR 3.6.1 | N/A | AIXM 5.1.1 does not have a dedicated attribute for the Identification of a Holding Procedure. The identifier of a holding will be the designator of the SignificantPoint used as holdingPoint, i.e. the DesignatedPoint.designator or the Navaid.designator. | ||
| Fix | 481 | Text | Identification of the holding procedure fix | Doc 10066 App 2 AIP ENR 3.6.1 | //aixm:HoldingPattern//aixm:holdingPoint//aixm:pointChoice_fixDesignatedPoint OR //aixm:HoldingPattern//aixm:holdingPoint//aixm:pointChoice_navaidSystem | In PANS-AIM ENR 3.6, the term holding fix is used for a navigation aid, in contrary to waypoint. In PANS-AIM Appendix 1, Fix is used for the Identification of the holding fix and Waypoint for the geographical location! There seems to be some inconsistency, also a Fix will have a geographical location and also a waypoint will have an Identification. Mapping is based on the assumption that one property is for the identification and the other for the position, regardless if it is a fix or a waypoint. The identifier of a holding procedure fix is the designator of the referenced DesignatedPoint or the Navaid. | |||
| Waypoint | 482 | Point | Geographical location of the holding waypoint | Doc 10066 App 2 AIP ENR 3.6.1 | //aixm:HoldingPattern//aixm:holdingPoint//aixm:pointChoice_fixDesignatedPoint OR //aixm:HoldingPattern//aixm:holdingPoint//aixm:pointChoice_navaidSystem | see PANS-AIM issue for Fix The geographical location of the holding waypoint is location of the referenced DesignatedPoint or the Navaid. Note that PANS-AIM has specific accuracy requirements for a holding waypoint which in AIXM 5 are coded by the horizontalAccuracy attribute of the referenced DesignatedPoint or the Navaid. | |||
| Inbound track | 483 | Bearing | The inbound track of the holding procedure | Doc 10066 App 2 AIP ENR 3.6.2 | //aixm:HoldingPattern//aixm:inboundCourse | ||||
| Turn Direction | 484 | Text | Direction of the procedure turn | Doc 10066 App 2 AIP ENR 3.6.3 | //aixm:HoldingPattern//aixm:turnDirection | ||||
| Speed | 485 | Value | Maximum indicated airspeed | Doc 10066 App 2 AIP ENR 3.6.4 | //aixm:HoldingPattern//aixm:speedLimit | ||||
| Level | Minimum holding level | 493 | Altitude | Minimum holding level of the holding procedure | Doc 10066 App 2 AIP ENR 3.6.5 | //aixm:HoldingPattern//aixm:lowerLimit, //aixm:HoldingPattern//aixm:lowerLimitReference | |||
| Maximum holding level | 494 | Altitude | Maximum holding level of the holding procedure | Doc 10066 App 2 AIP ENR 3.6.5 | //aixm:HoldingPattern//aixm:upperLimit, //aixm:HoldingPattern//aixm:upperLimitReference | ||||
| Time/distance outbound | 487 | Value | Time/distance value of the holding procedure | Doc 10066 App 2 AIP ENR 3.6.6 | //aixm:HoldingPattern//aixm:outboundLegSpan//aixm:endTime//aixm:HoldingPatternDuration//aixm:duration OR //aixm:HoldingPattern//aixm:outboundLegSpan//aixm:endDistance//aixm:HoldingPatternDistance//aixm:length | ||||
| Controlling unit | Name | 495 | Text | Indication of the controlling unit | Doc 10066 App 2 AIP ENR 3.6.7 | Unit.name | |||
| Frequency | 496 | Value | The operating frequency/channel of the controlling unit | Doc 10066 App 2 AIP ENR 3.6.7 | //aixm:InformationService//aixm:radioCommunication, //aixm:AirTrafficControlService//aixm:radioCommunication //aixm:RadioCommunicationChannel//aixm:frequencyTransmission, //aixm:RadioCommunicationChannel//aixm:frequencyReception, //aixm:RadioCommunicationChannel//aixm:channel | ||||
| Special holding entry procedure | 489 | Text | Textual description of the Special VOR/DME entry procedure | In case an entry radial to a secondary fix at the end of the outbound leg has been established for a VOR/DME holding pattern | Doc 10066 App 2 AIP ENR 1.5.1, AIP ENR 1.5.4, Doc 8168 Vol 2 Part II Section 4 1.5.1 | //aixm:HoldingPattern//aixm:instruction | |||
| AMA | Vertical limit | 447 | Altitude | Area Minimum Altitude (AMA) - The minimum altitude to be used under instrument meteorological conditions (IMC), that\nprovides a minimum obstacle clearance within a specified area, normally formed by parallels and meridians. | Annex 4 8.9.3, Annex 4 7.6.2 | ||||
| Lateral limits | 1200 | Distance | Lateral limits of the sectors | ||||||
| MVA | Vertical limit | 448 | Altitude | Minimum Vectoring Altitude | Annex 4 8.9.4, Annex 4 7.9.3.1.1, 21.9.3.1 | ||||
| Lateral limits | 1201 | Distance | Lateral limits of the sectors |