Text NOTAM production rules
...
the abbreviation RDN.BL. indicates that the corresponding data item must be taken from the RunwayDirection BASELINE;
the abbreviation RDN[O].BL indicated that the corresponding data item must be taken from the RunwayDirection BASELINE opposite to the RDN.BL.
the abbreviation RWY.BL. indicates that the corresponding data item must be taken from the Runway BASELINE associated with the RunwayDirection concerned;
the abbreviation AHP.BL. indicates that the corresponding data item must be taken from the AirportHeliport BASELINE associated with the Runway that is associated with the RunwayDirection concerned;
the abbreviation RCP.TD. indicates that the corresponding data item must be taken from the additional RunwayCentrelinePoint TEMPDELTA with role START_RUN that might have been created for the Event and which are associated with the same RunwayDirection that has the RDN.BL;the abbreviation RCP[O].TD. indicates that the corresponding data item must be taken from the additional RunwayCentrelinePoint TEMPDELTA that might have been created for the Event and which are associated with the opposite RunwayDirection RDN[O].BL;
In general, the ICAO DOC 8126 and the OPADD rules shall be followed. These have not been copied in this document in order to avoid duplication with those documents. Only instructions that are specific to the AIXM encoding of this event are stated here.
...
Declared Distance | Corresponding Q code |
|---|---|
Declared Distance Change | QMDCH |
Scope
Insert the value ‘A’.
Lower limit / Upper limit
Use “000/999”
Geographical reference
Insert the coordinate of the ARP (BL.ARP.ElevatedPoint) of the airport, formatted as follows:
the set of coordinates comprises 11 characters rounded up or down to the nearest minute; i.e. Latitude (N/S) in 5 characters; Longitude (E/W) in 6 characters;
the radius value is “005”.
Items B, C and D
Items B and C shall be decoded following the common production rules.
If at least one RCP.TD.associatedDeclaredDistante.RunwayDeclaredDistanceValue..timeInterval exists (the Event has an associated schedule), then it shall be represented in item D according to the common NOTAM production rules for {{Item D, E - Schedules}}. Otherwise, item D shall be left empty.
Item E
The following pattern should be used for automatically generating the E field text from the AIXM data:
...
Reference | Rule | |||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
(1) | If AD.BL.locationIndicatorICAO=YES, then ignore this branch. | |||||||||||||||||
(2) | Insert here the type of the airport decoded as follows
| |||||||||||||||||
(3) |
| |||||||||||||||||
Insert the word “unpaved” if RW.BL.SurfaceCharacteristics.composition has one of the values CLAY, CORAL, EARTH, GRASS, GRAVEL, ICE, LATERITE, MACADAM, SAND, SNOW, WATER, OTHER. Otherwise do not insert anything. | ||||||||||||||||||
(5) | If AD.BL.type=AD, LS or OTHER...insert here the declared distance type decoded as follows in the order TORA, TODA, LDA, ASDA.
If AD.BLtype=HP, insert here the declared distance type decoded as follows in the order below:
| |||||||||||||||||
(6) | Insert here the declared distance value followed by its unit of measurement decoded according to the {{text NOTAM production rules for distances}} If any of the declared distances is not applicable to the runway direction and therefore is not present in BASELINE and TEMPDELTA, it should be listed having the value “-” and no uom. | |||||||||||||||||
(7) | Annotations shall be translated into free text according to the followingencoding rules. |
Note: The objective is to fully automate generation, without human intervention. However, the implementers of the specification might consider reducing the cost of a fully automated generation by allowing the operator to fine-tune the text in order to improve its readability (with the inherent risk for human error, when re-typing is allowed).
...