Text NOTAM production rules
...
Reference | Data item (from coding scenario) | Rule | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
(1) | If AHP.BL.locationIndicatorICAO='YES', then ignore this branch. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
(2) | Insert here the type of the airport decoded as follows
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
(3) | airport name | a. If AHP.BL.name is not NIL, then insert it here. Otherwise, b. 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) | apron name | 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) | If more than one apron has a TEMPDELTA associated with the Event, then insert the designator of each additional apron designator preceded by ",". Insert "and" before the last entry. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
(6) | conditional for closed, except for prohibited for additionally allowed for | Insert hereTD.availability.ManoeuvringAreaAvailability.usage.ManoeuvringAreaUsage as follows:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
(7) | flight | Decode here each FlightCharacteristics property that was specified, as detailed below. If more than one FlightCharacteristics property was used, insert blanks between consecutive properties.
*Note: type is unlikely to be used in a NOTAM, its decoding is provided for completeness sake.
*Note: value is unlikely to be used in a NOTAM, its decoding is provided for completeness sake.
*Note: value is unlikely to be used in a NOTAM, its decoding is provided for completeness sake.
*Note: value is unlikely to be used in a NOTAM, its decoding is provided for completeness sake.
*Note: value is unlikely to be used in a NOTAM, its decoding is provided for completeness sake. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
(8) | aircraft | Decode here each AircraftCharacteristics property that was specified, as detailed below. If more than one AircraftCharacteristics property was used, insert blanks between consecutive properties.
*Note: value is unlikely to be used in a NOTAM, its decoding is provided for completeness sake.
**Note: new in AIXM 5.1.1. AircraftCharacteristics.wingSpan - insert the value followed by the value of the uom attribute. Prefix with the value of AircraftCharacteristics.wingSpanInterpretation, decoded as indicated in the following table:
*Note: value is unlikely to be used in a NOTAM, its decoding is provided for completeness sake. AircraftCharacteristics.weight - insert the value followed by the value of the uom attribute. Prefix with the value of AircraftCharacteristics.weightInterpretation, decoded as indicated in the following table:
*Note: value is unlikely to be used in a NOTAM, its decoding is provided for completeness sake. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
(9) | operation | Decode here the APN.TD.availability.usage.operation as follows:
*Note: value is unlikely to be used in a NOTAM, its decoding is provided for completeness sake. **Note: if all operations are affected, then either provide the text as described above or do not provide the text at all. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
(10) | PPR time PPR details | If TD.usage.priorPermission is not NIL, then insert here the decoding of the PPR information as detailed in the following diagram:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
(11) | If TD.usage.selection.logicalOperator=OR (there are more than one flight/aircraft combinations that are excepted), then select and decode each FlightCharacteristics/AircraftCharacteristics consecutively. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
(12) | If there exists a APN.TD.availability.annotation having propertyName="operationalStatus" and purpose='REMARK', then translate it into free text according to the decoding rules for annotations. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
(13) | Annotations of TD.ApronAreaAvailability shall be translated into free text according to the decoding rules for annotations. |
...
The eventual update of this type of event shall be encoded following the general rules for {{Event updates [archived] 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..
Code Block | ||||
---|---|---|---|---|
| ||||
template_cancel = ["(1)" "AHP.BL.type (2)" ("AHP.BL.name (3a)" | "AHP.BL.ARP (3b)") ] "\n" \n "Apron" "APN.BL.name" ["(5)" ("," | "and")] {"APN.BL.name" ["(5)" ("," | "and")]} ("resumed normal operations." [| " : New NOTAM to follow.(14)"]). |
The following pattern should be used for automatically generating the E field text from the AIXM data
Reference | Rule |
(14) | If the NOTAM will be followed by a new NOTAM concerning the same situation, then the operator shall have the possibility to specifychoose the "New NOTAM to follow" and this text shall be appended at the end of item E of the NOTAM Cbranch. 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”. |