...
Coding Rules for Marker Beacon
| Identifier | Data Encoding Rule | Justification | Data Verification Rule (UID) | Remarks |
|---|---|---|---|---|
| MKR-101 | The MarkerBeacon.designator attribute is mandatory. | Minimum AIP data set | TBD | |
| MKR-102 | The MarkerBeacon.name attribute is mandatory. | Minimum AIP data set | TBD | |
| MKR-103 | The MarkerBeacon.frequency attribute is mandatory. | Minimum AIP data set | TBD | |
| MKR-104 | The MarkerBeacon.location attribute is mandatory. | Minimum AIP data set | TBD | |
| MKR-105 | The NDB.designator shall not be duplicated within 600 NM of the location of the NDB. | EAD / ICAO Annex 11 | TBD | |
| MKR-106 | The value of the MarkerBeacon.frequency must be '75' 'MHz'. | EAD | TBD | |
| MKR-107 | The value of the NavaidComponent.markerPosition must be different for each MarkerBeacon that is used as NavaidComponent of the same Navaid instance wich type is equal-to 'ILS' or 'ILS_DME' or 'LOC' or 'LOC_DME' . | EAD | TBD | |
| NDB-108 | The geographical distance between the MarkerBeacon.location and the NDB.location used as NavaidEquipment for the same Navaid instance must be less than 100 metres. | EAD | TBD | |
| MKR-109 | No more than one MarkerBeacon may be co-located with same NDB. | EAD | TBD |
Coding Examples
TBD in the scope of the DONLON AIXM AIP data set.