...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Text NOTAM production rules
This section provides rules for the automated production of the text NOTAM message items, based on the AIXM 5.1.1 data encoding of the Event. Therefore, AIXM specific terms are used, such as names of features and properties, types of TimeSlices, etc:
...
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.
Item A
The item A shall contain the AD.BL.designator if AD.BL.locationIndicatorICAO='YES'. Otherwise, the nationality letter(s) as defined in ICAO Doc 7910 followed by “XX” or “XXX”.
Q code
The following mapping shall be used:
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) | Insert here the declared distance type decoded as follows in the order below. Only the RCP.TD.RunwayDeclaredDistance and RCP[n].BL.RunwayDeclaredDistance which do not have an associated Note with purpose=REMARK and the text="Baseline data copy. Not included in the NOTAM text generation" shall be included. If AHP.BL.type=AD, LS or OTHER
If AD.BLtype=HP
| ||||||||||||||||||
(6) | Insert here the declared distance value followed by its unit of measurement decoded according to the {{text NOTAM production rules for distances}} | ||||||||||||||||||
| (7) | If there are:
add here "Other declared distances unchanged.". Otherwise insert nothing. | ||||||||||||||||||
(8) | Annotations shall be translated into free text according to the rule for {{decoding annotations}}. |
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).
Items F & G
Leave empty.
Event Update
The eventual update of this type of event shall be encoded following the general rules for {{Event updates or cancellation}}, which provide instructions for all NOTAM fields, except for item E and the condition part of the Q code, in the case of a NOTAMC
...