NOTAM production rules
This section provides rules for the automated production of the text NOTAM message items, based on the AIXM 5.1 data encoding of the Event. Therefore, AIXM specific terms are used, such as names of features and properties, types of TimeSlices, etc:
...
The following patterns should be used for automatically generating the E field text from the AIXM data:
EBNF Code
Code Block | ||||
---|---|---|---|---|
| ||||
template = ("ACG.BL.type(1)" | "ASV.BL.type or category (2)" | "PSV.BL.type (3)") ("4" ("ACG.BLTD.ServiceOperationalStatus" | "ASV.BLTD.ServiceOperationalStatus" | "PSV.BLTD.ServiceOperationalStatus")) "." \n ["\n" "due to" "5" ("ACG.BLTD.annotation" | "ASV.BLTD.annotation" | "PSV.BLTD.annotation") "."] \n {"\n" "5" ("ACG.BLTD.annotation" | "ASV.BLTD.annotation" | "PSV.BLTD.annotation") "."}. |
Reference | Data item (from coding scenario) | Rule |
---|---|---|
(1) | type of airport ground service | Type of AircraftGroundService that is impacted shall be included, if present in ACG.BL.type. When type =
|
(2) | type of airport ground service | Type or category of AirportSuppliesService that is impacted shall be included, if present in ASV.BL.type or ASV.BL.category. When ASV.BL.Oxygen.type is not empty, then insert here the value or "Oxygen". When ASV.BL.Oil.category is not empty, then insert here the value followed by "oil" or insert the word "Oil" only. When ASV.BL.Fuel.category is not empty, then insert here the value preeceded by "Fuel" or insert the word "Fuel" only. |
(3) | type of airport ground service | Type of PassengerService that is impacted shall be included, if present in PSV.BL.type. When type =
|
(4) | operational status | If any of the ACG.BL, ASV.BL or PSV.BL services are indicated then .TD.ServiceOperationalStatus shall be inserted as "UNSERVICEABLE" or "NOT AVAILABLE". |
(5) | note | Annotations shall be translated into free text according to the decoding rules for Notes. |
Note: The objective is to full automatic 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).
...
The following pattern should be used for automatically generating the E field text from the AIXM data:
EBNF CodeEBNF
Code Block | ||||
---|---|---|---|---|
| ||||
template_cancel = ("ACG.BL.type(1)" | "ASV.BL.type or category (2)" | "PSV.BL.type (3)") ("4" ("ACG.TD.ServiceOperationalStatus" | "ASV.TD.ServiceOperationalStatus" | "PSV.TD.ServiceOperationalStatus")) ["New NOTAM to follow (6)"] "." \n
|
Reference | Rule |
---|---|
(6) | If the NOTAM will be followed by a new NOTAM concerning the same situation, then the operator shall have the possibility to specify "New NOTAM to follow" and this text shall be appended at the end of item E of the NOTAM C. Note: in this case, the 4th and 5th letters of the Q code shall also be changed into “XX” |