Text NOTAM production rules
...
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:
Code Block | ||||
---|---|---|---|---|
| ||||
template = ["(1)" "AHP.BL.type (2)" ("AHP.BL.name (3a)" | "AHP.BL.ARP (3b)") ] "\n" \n "Declared distances changed:" "\n" \n ["unpaved(4)"] "RWY" "RDN.BL.designator" "RCP.TD.RunwayDeclaredDistance.type(5)" "RCP.TD.RunwayDeclaredDistance.distance(6)" {"RCP.TD.RunwayDeclaredDistance.type(5)" "RCP.TD.RunwayDeclaredDistance.distance(6)"} "." \n ["\n" "Other declared distances unchanged.(7)"]\n ["\n" "RCP.TD.annotation(78)" "."]. |
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 AHP.BL.type=AD, LS or OTHER insert here the declared distance type decoded as follows in the order TORA, TODA, LDA, ASDA. Only the RCP.TD.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 AD.BLtype=HP, insert here the declared distance type decoded as follows in the order below:
If some declared distances are not affected by the temporary change and are kept with their BASELINE TimeSlices values, add after the listing of the changed values "Other declared distances unchanged." | ||||||||||||||||||
(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 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).
...