According to the revised Annex 15, digital AIS data sets are sub-typed as specified in 5.3.1.1.
“5.3.1.1 When provided, digital data shall be in the form of the following data sets:
a) AIP data set;
b) terrain data sets;
c) obstacle data sets;
d) aerodrome mapping data sets; and
e) instrument flight procedure data sets.
Note.— Detailed specifications concerning the content of the digital data sets are contained in the PANS-AIM (Doc 10066).”
The aeronautical information subjects that need to be included in each ICAO data set are specified in the PANS-AIM. For example, para 5.3.3.1.1 provides a list of subjects that need to be included in the AIP data set. An obstacle data set is specified as containing "obstacle feature types" according to the list of mandatory attributes provided in Appendix 6, Table A6-2. The content of the aerodrome mapping data sets is defined by reference to the Radio Technical Commission for Aeronautics (RTCA) Document DO 272D/European Organization for Civil Aviation Equipment (EUROCAE) Document ED 99 — User Requirements for Aerodrome Mapping Information. The PANS-AIM also contains the following note:
“5.3.3. Data Sets Note.— A data subject may appear in multiple data sets.”
The ICAO and industry provisions are relatively clear on the subjects that must to be included in a specific data set. The mapping of the AIP tables that may be removed if equivalent data is provided in a digital data set also provides a list of subjects that may be included in the AIP and Obstacle data sets.
However, there are no explicit ICAO provisions on subjects that shall not be included in a specific data set. For example, may an AIP data set contain also obstacles or SID/STAR procedures? The provisions for obstacle, airport mapping and terrain data sets existed already in the ICAO SARPS before the revised Annex 15. The common understanding is that an obstacle data set shall contain obstacles only, not terrain and not other AIS data. A similar common understanding exists for the terrain and airport mapping data sets.
The answer to this question is less obvious for the new AIP and Instrument Flight Procedures data sets because they have a larger scope in terms of feature types and also because of the relations/dependencies that exist between their subjects. For example, SID/STAR may refer to navaids, points airports, services, organisations, etc. By the fact that the revised Annex 15 provides separate specifications for the AIP data set and for the Instrument Flight Procedures data sets indicates that the ICAO intention was to not mix these topics. In addition, if any subject could appear in any data set could also create difficulties for the digital data set users. For example, if an AIP data set contained obstacles, the clients of the data sets would now know if such obstacles are just copies of data already contained in the dedicated Obstacle data set or additional obstacles that need also to be processed. Thus, declaring explicitly that some subjects (AIXM features) are not expected to appear in a specific data set will increase the interoperability and will decrease the workload of the data users. However, in order to enable IFP data sets to be used as stand-alone products, it should be allowed that AIXM features referenced from SID/STAR/Instrument Procedure are included in the IFP data sets.
Based on the above considerations, the following Table contains the allocation of various AIXM features to the Digital ICAO Data Set categories. The following terms are used:
if the AIP Data Set is not yet provided, then AirportHeliport instances referenced by an ObstacleArea shall be included in the Obstacle data set concerned. Otherwise, this data would be not available;
AIXM Feature | AIP Data Set | Aerodrome Mapping | Instrument Flight
| Obstacle Data Set | Remarks
| ||
---|---|---|---|---|---|---|---|
AerialRefuelling | N/A | N/A | N/A | ||||
AeronauticalGroundLight | Optional | N/A | N/A | ||||
AircraftGroundService | N/A | N/A | N/A | ||||
AircraftStand | N/A | Mandatory | N/A | ||||
AirportClearanceService | N/A | N/A | N/A | ||||
AirportHeliportCollocation | N/A | N/A | N/A | ||||
AirportHeliport | Mandatory | Mandatory | Conditional | ||||
AirportHotSpot | N/A | Optional | N/A | AMD DS: This is optional as not all aerodromes will have one. | |||
AirportProtectionAreaMarking | N/A | N/A | N/A | ||||
AirportSuppliesService | N/A | Mandatory | N/A | AMD DS: This is mandatory in order to be able to create a complete aerodrome mapping database. | |||
AirspaceBorderCrossing | N/A | N/A | N/A | ||||
Airspace | Mandatory | N/A | N/A | ||||
AirTrafficControlService | Optional | N/A | N/A | ||||
AirTrafficManagementService | Optional | N/A | N/A | ||||
AltimeterSource | N/A | N/A | N/A | ||||
AngleIndication | Optional | N/A | N/A | AIP DS: Even if explicitly required by the PANS-AIM, it is possible that for some States there is no DistanceIndication defined for their en-route fixes | |||
ApproachLightingSystem | N/A | Mandatory | N/A | ||||
ApronElement | N/A | Mandatory | N/A | ||||
ApronLightSystem | N/A | Mandatory | N/A | ||||
ApronMarking | N/A | N/A | N/A | ||||
Apron | N/A | Mandatory | N/A | AMD DS: This is mandatory in order to be able to create a complete aerodrome mapping database. | |||
ArrestingGear | N/A | Mandatory | N/A | ||||
ArrivalFeederLeg | N/A | N/A | N/A | ||||
ArrivalLeg | N/A | N/A | N/A | ||||
AuthorityForAirspace | Optional | N/A | N/A | ||||
Azimuth | Optional | N/A | N/A | AIP DS: Unlikely to exist in most States (MLS equipment component) | |||
ChangeOverPoint | Optional | N/A | N/A | ||||
CheckpointINS | N/A | N/A | N/A | ||||
CheckpointVOR | N/A | N/A | N/A | ||||
CirclingArea | N/A | N/A | N/A | ||||
DeicingAreaMarking | N/A | N/A | N/A | ||||
DeicingArea | N/A | Optional | N/A | AMD DS: This is optional as not all aerodromes will have one. | |||
DepartureLeg | N/A | N/A | N/A | ||||
DesignatedPoint | Mandatory | N/A | N/A | ||||
DirectionFinder | Optional | N/A | N/A | ||||
DistanceIndication | Optional | N/A | N/A | AIP DS: Even if explicitly required by the PANS-AIM, it is possible that for some States there is no DistanceIndication defined for their en-route fixes | |||
DME | Mandatory | N/A | N/A | ||||
Elevation | Optional | N/A | N/A | AIP DS: Unlikely to exist in most States (MLS equipment component) | |||
FinalLeg | N/A | N/A | N/A | ||||
FireFightingService | N/A | N/A | N/A | ||||
FlightRestriction | N/A | N/A | N/A | ||||
FloatingDockSite | N/A | N/A | N/A | ||||
GeoBorder | Optional | N/A | N/A | ||||
Glidepath | Mandatory | N/A | N/A | ||||
GroundTrafficControlService | N/A | Mandatory | N/A | ||||
GuidanceLineLightSystem | N/A | Mandatory | N/A | ||||
GuidanceLineMarking | N/A | Mandatory | N/A | ||||
GuidanceLine | N/A | Mandatory | N/A | AMD DS: This is mandatory in order to be able to create a complete aerodrome mapping database. | |||
HoldingAssessment | N/A | N/A | N/A | ||||
HoldingPattern | Optional | N/A | N/A | ||||
InformationService | Optional | N/A | N/A | ||||
InitialLeg | N/A | N/A | N/A | ||||
InstrumentApproachProcedure | N/A | N/A | N/A | ||||
IntermediateLeg | N/A | N/A | N/A | ||||
Localizer | Mandatory | N/A | N/A | ||||
MarkerBeacon | Optional | N/A | N/A | ||||
MarkingBuoy | N/A | N/A | N/A | ||||
MissedApproachLeg | N/A | N/A | N/A | ||||
Navaid | Mandatory | N/A | N/A | ||||
NavigationAreaRestriction | N/A | N/A | N/A | ||||
NavigationArea | N/A | N/A | N/A | ||||
NDB | Mandatory | N/A | N/A | ||||
NonMovementArea | N/A | N/A | N/A | ||||
ObstacleArea | N/A | N/A | Mandatory | ||||
OrganisationAuthority | Optional | N/A | Conditional | ||||
PassengerLoadingBridge | N/A | N/A | N/A | ||||
PassengerService | N/A | N/A | N/A | ||||
PilotControlledLighting | N/A | N/A | N/A | ||||
PrecisionApproachRadar | N/A | N/A | N/A | ||||
PrimarySurveillanceRadar | N/A | N/A | N/A | ||||
ProcedureDME | N/A | N/A | N/A | ||||
RadarSystem | N/A | N/A | N/A | ||||
RadioCommunicationChannel | Optional | Mandatory | N/A | AMD DS: This is mandatory in order to be able to create a complete aerodrome mapping database. | |||
RadioFrequencyArea | Optional | N/A | N/A | ||||
Road | N/A | Mandatory | N/A | ||||
RouteDME | N/A | N/A | N/A | ||||
RouteSegment | Mandatory | N/A | N/A | ||||
Route | Mandatory | N/A | N/A | ||||
RulesProcedures | N/A | N/A | N/A | ||||
RunwayBlastPad | N/A | Mandatory | N/A | ||||
RunwayCentrelinePoint | Mandatory | Mandatory | N/A | ||||
RunwayDirectionLightSystem | N/A | Mandatory | N/A | ||||
RunwayDirection | Mandatory | Mandatory | Conditional | AMD DS: This is mandatory in order to be able to create a complete aerodrome mapping database. | |||
RunwayElement | N/A | Mandatory | N/A | ||||
RunwayMarking | N/A | Mandatory | N/A | ||||
RunwayProtectAreaLightSystem | N/A | N/A | N/A | ||||
RunwayProtectArea | N/A | Mandatory | N/A | ||||
Runway | Mandatory | Mandatory | N/A | ||||
RunwayVisualRange | N/A | N/A | N/A | ||||
SafeAltitudeArea | N/A | N/A | N/A | ||||
SDF | Optional | N/A | N/A | AIP DS: Unlikely to exist in most States | |||
SeaplaneLandingArea | N/A | N/A | N/A | ||||
SeaplaneRampSite | N/A | N/A | N/A | ||||
SearchRescueService | Optional | N/A | N/A | ||||
SecondarySurveillanceRadar | N/A | N/A | N/A | ||||
SignificantPointInAirspace | N/A | N/A | N/A | ||||
SpecialDate | Optional | N/A | N/A | ||||
SpecialNavigationStation | Optional | N/A | N/A | ||||
SpecialNavigationSystem | Optional | N/A | N/A | ||||
StandardInstrumentArrival | N/A | N/A | N/A | ||||
StandardInstrumentDeparture | N/A | N/A | N/A | ||||
StandardLevelColumn | Optional | N/A | N/A | ||||
StandardLevelSector | Optional | N/A | N/A | ||||
StandardLevelTable | Optional | N/A | N/A | ||||
StandMarking | N/A | N/A | N/A | ||||
SurveyControlPoint | N/A | Mandatory | N/A | ||||
TACAN | Optional | N/A | N/A | AIP DS: Unlikely to exist in most States, as it is a military navaid | |||
TaxiHoldingPositionLightSystem | N/A | Mandatory | N/A | ||||
TaxiHoldingPositionMarking | N/A | Mandatory | N/A | ||||
TaxiHoldingPosition | N/A | Mandatory | N/A | AMD DS: This is mandatory in order to be able to create a complete aerodrome mapping database. | |||
TaxiwayElement | N/A | Mandatory | N/A | ||||
TaxiwayLightSystem | N/A | Mandatory | N/A | ||||
TaxiwayMarking | N/A | Mandatory | N/A | ||||
Taxiway | N/A | Mandatory | N/A | AMD DS: This is mandatory in order to be able to create a complete aerodrome mapping database. | |||
TerminalArrivalArea | N/A | N/A | N/A | ||||
TouchDownLiftOffLightSystem | N/A | Mandatory | N/A | ||||
TouchDownLiftOffMarking | N/A | N/A | N/A | ||||
TouchDownLiftOffSafeArea | N/A | N/A | N/A | ||||
TouchDownLiftOff | Mandatory | Mandatory | N/A | ||||
Unit | Optional | N/A | N/A | ||||
UnplannedHolding | N/A | N/A | N/A | ||||
VerticalStructure | N/A | Mandatory | Mandatory | AMD DS: Aerodrome Mapping Data Sets contain a VerticalStructure when it is "located within an area that extends from the edge(s) of the runway(s) to 90m from the runway centerline(s) and for all other parts of the aerodrome movement area(s), 50m from the edge(s) of the defined area(s)." This includes, for example, terminal buildings, hangars, windsocks and fences. Not all of the VerticalStructures will qualify as obstacles in any ObstacleArea. However, there may be overlaps with the content of the Obstacle Data Set. | |||
VisualGlideSlopeIndicator | N/A | Mandatory | N/A | ||||
VOR | Mandatory | N/A | N/A | ||||
WorkArea | N/A | Optional | N/A | AMD DS: This is optional as not all aerodromes will have one. |