Supporting material for ICAO Aerodrome Mapping Data Sets
v1.0.6
This page outlines the scope of AMX.
Features
AMX includes the following features that are not present in AIXM 5.1.1. All of the features' attributes are in the extension.
- AerodromeSign correspondence
- ATCBlindSpot correspondence
- BridgeSide correspondence
- DeicingGroup correspondence
- PositionMarking correspondence
- Water correspondence
Attributes
AMX includes the following attributes that are not present in AIXM 5.1.1 even if a feature is.
Feature | Attributes |
---|---|
AerodromeReferencePoint correspondence | systems, mintelev, maxtelev, devtelev, maxtgrad, devtgrad, avgtelev |
DeicingArea correspondence | featbase, lvo, deicegrp |
FrequencyArea correspondence | geopoly |
Hotspot correspondence | hstext1, hstext2 |
LandAndHoldShortOperationLocation correspondence | idp, idthr, lahsotyp, holddir |
ParkingStandArea correspondence | termref |
ParkingStandLocation correspondence | termref |
RunwayDisplacedArea correspondence | lvo |
RunwayElement correspondence | lvo |
RunwayExitLine correspondence | exittype, idrwy |
RunwayIntersection correspondence | lvo |
RunwayThreshold correspondence | lvo, tohlight, alstype |
StandGuidanceLine correspondence | termref |
TaxiwayElement correspondence | idcross, idinter, lvo, featbase, idbase |
TaxiwayHoldingPosition correspondence | rwyahtxt, holddir, aippub, marktype, lvo, rwelight |
TaxiwayIntersectionMarking correspondence | holddir, marktype, aippub, idp |
Notes
lvo | only airport can be the true source of this info. However, structurally, the extension covers it. extension will need a scope statement. clarify the use of this with some providers e.g. Lufthansa Systems once agree scope of the extension see if lvo is in scope |
Overview
Content Tools