...
Purpose and Scope
These pages contain the AIXM coding guidelines for the minimum and conditional data items of the AIP data set for the Radio navigation aid subject as defined in PANS-AIM.
| Tip | ||
|---|---|---|
| ||
In an AIP, corresponding Radio navigation aid information may be published in the following sections:
|
AIXM Model Overview
| Include Page | ||||
|---|---|---|---|---|
|
| Info | ||
|---|---|---|
| ||
A change proposal (AIXM-402) for the next AIXM 5.2 version has been approved by the AIXM Change Control Board, which allows the addition of ICAO country code as an attribute. The coding guidelines provided here are aligned with forward/backward conversion rules contained in the AIXM-402 Change Proposal. |
| Info | ||
|---|---|---|
| ||
A change proposal (AIXM-467) for the next AIXM 5.2 version has been approved by the AIXM Change Control Board, in which additional classes, associations and data types are added in the model representing elements of the GNSS. The coding guidelines provided here are aligned with forward/backward conversion rules contained in the AIXM-467 Change Proposal. |
Coding Example
The figure blow below shows a simple example of a collocated "VOR/DME" with the designator "BOZ" and the name "BERG-OP-ZEE".
It consists of two navaid equipments, a VOR and a DME. Both of them have the desigantor designator "BOZ".
Both have the same defined magentic magnetic variation and are operational H24.
The VOR and the DME DME are located ast at the same position. Only the DME has a defined elevation , of "30 meters".
Also, the Navaid has a location which, as there is no delocationdislocation, is the same as the one for the navaid equipments.
...
The VOR does have a frequency, whereas for the DME a cooresponding corresponding channel is defined.
The VOR in addition has a defined declicationdeclination.
Also, the Coverage of the VOR and/or DME may be provided (note that this information is not required for the minimum/conditional AIP data set).
...
The figure below shows the encoding of one of the referenced navaidEquiment navaidEquipment of the figure above, viz. the VOR "DON"
The location is the same as for the Navaid.
More
examples to TBD in the scope of the DONLON AIXM AIP data set.Coding examples can also be found in the AIP Data Set - Specimen (DONLON):
| No. | Description | XPath Expression |
|---|---|---|
NAV-EX-01 VOR-EX-01 DME-EX-01 | VOR/DME (incl. served aerodrome) | //aixm:NavaidTimeSlice [@gml:id ='NAV_BOR'] | //aixm:VORTimeSlice [@gml:id ='VOR_BOR'] | //aixm:DMETimeSlice [@gml:id ='DME_BOR'] |
NAV-EX-02 VOR-EX-02 | VOR | //aixm:NavaidTimeSlice [@gml:id ='NAV_EKO'] | //aixm:VORTimeSlice [@gml:id ='NAV_EKO'] |
NAV-EX-03 NDB-EX-01 | NDB (enroute) | //aixm:NavaidTimeSlice [@gml:id ='NAV_NDB_DON'] | //aixm:NDBTimeSlice [@gml:id ='NDB_DON'] |
NAV-EX-04 NDB-EX-02 | NDB (Locator) | //aixm:NavaidTimeSlice [@gml:id ='NAV_KL'] | //aixm:NDBTimeSlice [@gml:id ='NDB_KL'] |
NAV-EX-05 NDB-EX-03 MKR-EX-01 | NDB collocated with Marker Beacon | //aixm:NavaidTimeSlice [@gml:id ='NAV_SCN'] | //aixm:NDBTimeSlice [@gml:id ='NDB_SCN'] | //aixm:MarkerBeaconTimeSlice [@gml:id ='MKR_SCN'] |
NAV-EX-06 LLZ-EX-01 GPT-EX-01 NDB-EX-02 MKR-EX-02 MKR-EX-03 | ILS with MM and LOM | //aixm:NavaidTimeSlice [@gml:id ='NAV_OXS'] | //aixm:LocalizerTimeSlice [@gml:id ='LLZ_OXS'] | //aixm:GlidepathTimeSlice [@gml:id ='GPT_OXS'] | //aixm:NDBTimeSlice [@gml:id ='NDB_KL'] | //aixm:MarkerBeaconTimeSlice [@gml:id ='MKR_OM27R'] | //aixm:MarkerBeaconTimeSlice [@gml:id ='MKR_MM27R'] |
Child Pages
| Child pages (Children Display) |
|---|
...