Item A
The item A shall be generated according to the general production rules for item A using the Event.concernedAirportHeliport.
Item Q
Apply the common NOTAM production rules for item Q, complemented by the following specific rules for this particular scenario:
Q code
Insert QMRLL.
Scope
Insert the value ‘A’.
Lower limit / Upper limit
Use “000/999”
Geographical reference
Insert the coordinate of the ARP (AHP.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 RWE.BL.ManoeuvringAreaAvailability.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
["unpaved(4)"] "RWY.BL.type(5)" ("RWY.BL.designator(6)" | "RDN.BL.designator(6)") \n
"closed" "RWE.BL.annotation(7)" ["due to" "RWE.BL.availability.annotation(8)"]\n
{"\n" "RWE.BL.annotation(9)" "."} ["."]. |
Reference | Data item (from coding scenario) | Rule | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
(1) | airport designator | If AHP.BL.locationIndicatorICAO is not null, then ignore this branch. | ||||||||
(2) | Insert here the type of the airport decoded as follows
| |||||||||
(3) | (a) If AHP.BL.name is not NIL, then insert it here. (b) Otherwise insert here the text "located at" followed by the AHP.BL.ARP.ElevatedPoint decoded according to the text NOTAM production rules for aixm:Point | |||||||||
(4) | runway surface composition | Insert the word “unpaved” if RWY.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 type of the Runway decoded as follows
| |||||||||
| (6) | runway/runway direction | Depending on the input, RWY.BL.designator or RDN.BL.designator shall be inserted here. Note: this information about the runway direction that is operationally impacted, if applicable, is not part of the AIXM coding. If no such data is available (for example, when post-digitising NOTAM received from world-wide, then the RWY.BL.designator shall be used by default. | ||||||||
(7) | extent closed | Insert here the RWE.BL.annotation note with propertyName='extent' and purpose='DESCRIPTION' translated into free text according to the decoding rules for annotations. | ||||||||
| (7) | closure reason | Insert here the RWE.BL.availability.ManoeuvringAreaAvailability.annotation with propertyName='operationalStatus' and purpose='REMARK' translated into free text according to the decoding rules for annotations. | ||||||||
(8) | note | Other RWE.BL.annotation 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.
If a NOTAMC is produced, then the 4th and 5th letters (the "condition") of the Q code shall be "AK" unless there is a new NOTAM to follow, in which case the Q code shall be “XX”.
The following pattern should be used for automatically generating the E field text from the AIXM data:
| Code Block | ||||
|---|---|---|---|---|
| ||||
template_cancel = ["(1)" "AHP.BL.type (2)" ("AHP.BL.name (3a)" | "AHP.BL.ARP (3b)")] "\n" \n ["unpaved (4)"] "RWY" ("5.BL.Type(5)" ("RWY.BL.designator(6)" | "RDN.BL.designator(6)")) ("resumed normal operations." | "\n" \n [": New NOTAM to follow .(9)"]"."). |
Reference | Rule |
|---|---|
(9) | If the NOTAM will be followed by a new NOTAM concerning the same situation, then the operator shall have the possibility to specify choose the "NEW New NOTAM TO FOLLOW" and this text shall be appended at the end of item E of the NOTAM Cto follow" branch. This branch cannot be selected automatically because this information is only known by the operator. Note: in this case, the 4th and 5th letters of the Q code shall also be changed into “XX”. |