...
type. identification, name, aerodrome served, hours of operation, magnetic variation, frequency/channel, position, elevation, magnetic bearing, true bearing, zero bearing direction...
The diagram below shows the AIXM classes, including the relevant data types, needed to encode that information:
...
For instance, a VOR that is serving two different approaches for two different Aerodromesairports, will be assigned to both airports.
This association is established via the Navaid.servedAirport property, i.e. not the individual navaid equipment is related to the airport/heliport but the whole navaid system (e.g. the VOR/DME and not the VOR and the DME).
ILS and MLS are associated to a certain runway/FATO direction of an airport/heliport (see topics Localizer, Glidepath and MLSIn an AIP navaids that serve an airport/heliport are published in section AD2.19 /AD 3.18 Radio navigation and landing aids.
Runway Direction Served
This information is not required by PANS-AIM as minimum/conditional data of the AIP data set (but it is listed in PANS-AIM Appendix 1). Landing aids, such as an ILS, which in AIXM 5 is coded as an istance of the Navaid class will be related to a RunwayDirection via the Navaid.runwayDirection property.
In an AIP navaids that are situated at a runway direction are published in section AD2.19 /AD 3.18 Radio navigation and landing aids.
Significant Point
in AIXM 5 the instance of a Navaid class is related to the SignificantPoint class (see also topic SignificantPoint [SPN]). The Significant point may be uses as start or end point of a route or terminal procedure, or the centre point of a TAA/MSA, to describe the horizontal border of an airspace, etc.
Hence, navaids that are used as significant point have to be encoded using the Navaid class, whereas other navaids may be just encoded as NavigationEquipment (e.g. a marker that is part of an ILS installation).
Coding Rules for Basic Data for Navaid
| Identifier | Data Encoding Rule | Justification | Data Verification Rule (UID) | Remarks | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| NAV-101 | The Navaid.type attribute is mandatory. | Minimum AIP data set | TBD | |||||||||||
| The Navaid.name attribute is mandatory. | Minimum AIP data set | TBD | ||||||||||||
| The Navaid.designator attribute is mandatory. | Minimum AIP data set | TBD | Some types of navaid do not have designator( e.g. Glidepath) | |||||||||||
| The NavaidEquipment.name attribute shall be encoded if available. | Minimum AIP data set | TBD | Some types of navaid do not have name (e.g. Glidepath).
| |||||||||||
| The NavaidEquipment.designator attribute shall be encoded if available. | Minimum AIP data set | TBD | Some types of navaid do not have designator (e.g. Glidepath).
| |||||||||||
| If the Navaid.purpose is equal-to 'TERMINAL' or 'BOTH' the either the Navaid.servedAirport or the Navaid.servedRunwayDirection shall be coded. | Minimum AIP data set (for Aiport) PANS-AIM (Runway Direction) | TBD |
| |||||||||||
| If the Navaid.purpose is equal-to 'ENROUTE' neither the Navaid.servedAirport nor the Navaid.servedRunwayDirection shall be coded. | Data consistency | TBD | ||||||||||||
| Each instance of a Navaid shall be composed as a minimum of one NavaidEquipment. | Data consistency | TBD |
Coding Examples
See topic Navaid [NAV]
...