...
| Tip | ||
|---|---|---|
| ||
The example below shows the publication of a "ghost frequency" of a DME in ENR 4.1
|
| Info | ||
|---|---|---|
| ||
A change proposal (AIXM-543) for the next AIXM 5.2 version has been approved by the AIXM Change Control Board, where the DME ghostFrequency attribute is tuningFrequencyVHF. The coding guidelines provided here are aligned with forward/backward conversion rules contained in the AIXM-543 Change Proposal. |
Navaid Collocation
A DME may be co-located with one and only one VOR or NDB. In this case the corresponding Navaid feature will reference the DME as navaidEquipment.
...
For more details see Landing Systems & Navaid Collocation.
Coding Rules for DME
...
.
...
The geographical distance between the DME.location and the VOR.location which are used to compose the same Navaid must be:
a) less than 30 metres if the VOR is located at an aerodrome/heliport (connected through Navaid.servedAirport) and has VOR.type equal-to 'DVOR';
b) less than 80 metres if the VOR is located at an aerodrome/heliport (connected through Navaid.servedAirport) and has VOR.type equal-to 'DVOR';
c) less than 600 metres if the VOR is not located at an aerodrome/heliport (not through Navaid.servedAirport).
...
Coding Examples
Coding examples can also be found in the AIP Data Set - Specimen (DONLON):
...