...
In AIXM 5, the instance of a Navaid class is related to the SignificantPoint class (see also topic SignificantPoint (Overview)). The Significant point may be used 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.
...
| Identifier | Data Encoding Rule | Justification | Data Verification Rule (UID) | Remarks | ||||||
|---|---|---|---|---|---|---|---|---|---|---|
| NAV-101 | The Navaid.type attribute is mandatory. | Minimum AIP data set | AIXM-5.1_RULE-1A33DB | |||||||
| NAV-102 | The Navaid.name attribute is mandatory. | Minimum AIP data set | TBD |
| ||||||
| NAV-103 | The Navaid.designator attribute is mandatory. | Minimum AIP data set | TBD| Info | | ||||||
| ||||||||||
| NAV-903 | The Navaid.purpose attribute is mandatory. | Operational Need | TBD | Decision made by AIXM Coding FG (see also solved comments) | ||||||
| NAV-104 | If the Navaid.purpose is equal-to 'TERMINAL' or 'ALL' at least one of the following shall be coded Navaid.servedAirport and/or the Navaid.servedRunwayDirection. | Minimum AIP data set (for Airport) PANS-AIM (Runway Direction) | TBD | |||||||
| NAV-105 | If the Navaid.purpose is equal-to 'ENROUTE' neither the Navaid.servedAirport nor the Navaid.servedRunwayDirection shall be coded. | Data consistency | TBD | |||||||
| NAV-106 | Each instance of a Navaid shall be composed as a minimum of one NavaidEquipment. | Data consistency | Several rules ( e.g. AIXM-5.1_RULE-1B1D6D, AIXM-5.1_RULE-1B1D69) |
...