...
DME Designator & Name
In general, a DME will carry a three letter character identifier. The DME.designator attribute is used to code that data.
In case the DME is collocated with a VOR it will have same designator as the VOR.
The long name given to the DME is coded using the DME.name attribute.
...
PANS-AIM does not require the type of the DME to be provided. However, PANS-AIM requires different accuracy values for the elevation of a DME depending on its type. As elevation for the DME is part of the minimum AIP data set the type has to be known. In AIXM the tye is coded using the DME.type attribute. The typr defines the particular spectrum characteristics or accuracy of the DME. The list of values for the CodeDMEType class contains:
| Value | Description |
|---|---|
| 'NARROW' | DME/N, narrow spectrum characteristics. |
| 'PRECISION' | DME/P, improved accuracy compared to DME/N |
| 'WIDE' | DME/W, wide spectrum characteristics. |
| 'OTHER' | Other. |
Aerodrome Served
See topic Basic Data for Navaid.
...
See topic Facility coverage.
Navaid Collocation
...
A DME may be co-located with one and only one VOR or NDB.
In the AIP collocated VOR and DME Navaids are usually referred to as VOR/DME or DVOR/DME.
There are certain ICAO rules with regard to the relative distance between the VOR and the DME, frequency pairing and coded identifier. They are mentioned as coding rules.
A DME (and VOR) may only maintain a single collocation relationship at a time, which means that it is not possible to collocate a VOR with two different DMEs, and vice versa. The same is valid for a DME and NDB collocation.
For more details see topic Landing Systems & Navaid Collocation.
Coding Rules for DME
| Identifier | Data Encoding Rule | Justification | Data Verification Rule (UID) | Remarks | |||||
|---|---|---|---|---|---|---|---|---|---|
| DME-101 | The DME.designator attribute is mandatory. | Minimum AIP data set | TBD | ||||||
| DME-102 | The DME.name attribute is mandatory. | Minimum AIP data set | TBD | ||||||
| DME-103 | The DME.channel attribute is mandatory. | Minimum AIP data set | TBD | ||||||
| DME-104 | For DME ElevatedPoint.elevation is mandatory. | Minimum AIP data set | TBD | ||||||
| DME-105 | For DME ElevatedPoint.accuracy should be provided. | PANS-AIM | TBD | ||||||
| DME-106 | For DME ElevatedPoint.verticalDatum should be provided. | PANS-AIM | TBD | ||||||
| DME-107 | No more than one DME may be co-located with same VOR. | EAD/ Data consistency | TBD |
| |||||
| DME-108 | A DME and a TACAN cannot be collocated to the same VOR. | EAD/ Data consistency | TBD | ||||||
| DME-109 | The DME.designator shall not be duplicated within 600 NM of the location of the DME. | EAD / ICAO Annex 11 | TBD | ||||||
| DME-110 | If DME.channel is not specified, then DME.ghostFrequency must be specified. | EAD | TBD | ||||||
| DME-111 | DME.ghostFrequency cannot be specified if the DME is collocated with a VOR or is part of an ILS or MLS system. | EAD / ICAO Annex 11 | TBD | ||||||
| DME-112 | DME.ghostFrequency must be consistent with the DME.channel value, according to Table A, ICAO Annex 10, Vol. 1. | EAD / ICAO Annex 11 | TBD | ||||||
| DME-113 | The value of the DME.channel must be paired with the VOR.frequency of the related VOR, as described by Table A, ICAO Annex 10, Vol.1. | EAD / ICAO Annex 10 | TBD |
Coding Examples
TBD