Decoding
Text NOTAM production rules
...
Reference | Rule | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
(1) | If AHP.BL.locationIndicatorICAO=YES, 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. 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) | Insert here the APN.annotation and/or APE.annotation note with purpose="DESCRIPTION" stored in the BASELINE data (e.g. “between Acft stand 1 and Acft stand 5”). If more than one ApronElement has a TEMPDELTA associated with the Event, then the application shall identify the connected elements and generate the text in a logical order (e.g. "between Acft stand 1 and Acft stand 10" could be generated from two ApronElements - one from Acft stand 1-5 and one from 5-10) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
(5) | If more than one apron and/or apron element has a TEMPDELTA associated with the Event, then insert the designator of each additional apron and/or apron element, designator preceded by ",". Insert "and" before the last entry. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
(6) | If there exists a APN.TD.availability.annotation or APE.TD.availability.annotation having propertyName="operationalStatus" and purpose="REMARK", then translate it into free text according to the decoding rules for annotations. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
(7) | If there exist one or more TD.availability.usage then decode them following this branch, in the following order of priorities:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
(8) | If TD.usage.priorPermission is not NIL, then insert here the decoding of the PPR information as detailed in the following diagram:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
(9) | 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. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
(10) | 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. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
(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) | Annotations of TD.ApronAreaAvailability shall be translated into free text according to the decoding rules for annotations. |
...
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)") ("Apron," | "APN.BL.name"and")]} "resumed normal operations." ["New NOTAM to follow.(13)"]. |
...