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 here QMNLC
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 APE.BL.availability.ApronAreaAvailability.timeInterval exists (i.e. the Event has an associated schedule), then all such Timesheet(s) shall be represented in item D according to the common NOTAM production rules for {tem D, E - Schedules. Otherwise, item D shall be left empty.
Item E
The following pattern should be used as a base for 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 "apronApron (4)" "APN.BL.name" "closed" "APE.BL.annotation (5)" "\n" \n
[ "due to" "APE.BL.availability.annotation (6)"]\n
{"\n" "APE.BL.annotation(7)" "."} ["."]. |
Reference | Data item (from coding scenario) | Rule | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
(1) | 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 null, 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) | For the potential applications/implementations - the word "apron" may appear twice depending on the coded APN.BL.name (e.g. Apron MILITARY APRON or apron APRON A1). Caution shall be exercised for NOTAM production to avoid possible duplications. | |||||||||
| (5) | location and extent description | Insert here the APE.annotation note with propertyName=extent and purpose=DESCRIPTION translated into free text according to the decoding rules for annotations. | ||||||||
| (6) | closure reason | Insert here the ApronElement/ApronAreaAvailability.annotation with propertyName="operationalStatus" and purpose="REMARK" translated into free text according to the decoding rules for annotations. | ||||||||
(7) | note | Other annotations of APE.BL shall be translated into free text according to the decoding rules for annotations. |
Items F & G
Leave empty.
Event Update
The eventual update of this type of event shall be encoded following the general rules for Event update 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", except for the situation of a “new NOTAM to follow, in which case “XX”shall be used.
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)") ] "apron" "APN.BL.name" ("resumed normal operations." | " : New NOTAM to follow.(7)"). |
Reference | Rule |
(7) | If the NOTAM will be followed by a new NOTAM concerning the same situation, then the operator shall have the possibility to choose the "New NOTAM to 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”. |