Text NOTAM production rules

This section provides rules for the automated production of the text NOTAM message items, based on the AIXM 5.1.1 data encoding of the Event. Therefore, AIXM specific terms are used, such as names of features and properties, types of TimeSlices, etc:

  • the abbreviation APN.BL. indicates that the corresponding data item must be taken from the Apron BASELINE;

  • the abbreviation APN.TD. indicates that the corresponding data item must be taken from the Apron TEMPDELTA that was created for the Event.

  • the abbreviation AHP.BL. indicates that the corresponding data item must be taken from the AirportHeliport BASELINE associated with the Apron that is associated with the ApronElement concerned;

In general, the ICAO DOC 8126 and the OPADD rules shall be followed. These have not been copied in this document in order to avoid duplication with those documents. Only instructions that are specific to the AIXM encoding of this event are stated here.

Item A

The item A shall be generated according to the general production rules for item A using the Event.concernedAirportHeliport.

Q code

Insert 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 APN.TD.availability.ApronAreaAvailability.timeInterval or APE.TD.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 {{Item D, E - Schedules}}. Otherwise, item D shall be left empty.

Item E

If apron elements are used, the automatic generation of an easy human-readeable NOTAM text is practically impossible using just the AIXM encoding. Some pre-defined groups of ApronElements could be pre-defined in the application, which would then generate directly the desired text, such as "between A and C", "between A and D", etc. This is considered a limitation of this scenario - although the Digital NOTAM is accurate, the NOTAM text but cannot be automatically re-generated by the end user based on just the AIXM code.

The following pattern should be used as a base for generating the E field text from the AIXM data:

EBNF Code
template = ["(1)" "AHP.BL.type (2)" ("AHP.BL.name (3a)" | "AHP.BL.ARP (3b)")] \n "Apron (4)" "APN.BL.name" ["(5)" ("," | "and")] {"APN.BL.name"  ["(5)" ("," | "and")]}
\n "closed" [ "due to" "APN.TD.availability.annotation (6)"]\n
{"\n" "APN.TD.availability.annotation(7)" "."} ["."].

Reference

Rule

(1)

If AHP.BL.locationIndicatorICAO=YES, then ignore this branch.

(2)

Insert here the type of the airport decoded as follows

AHP.BL.type

Text to be inserted in Item E

AD or AH

"AD"

HP

"Heliport"

LS or OTHER

"Landing site"

(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)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)

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.

(7)

Annotations of TD.ApronAreaAvailability 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 [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..

EBNF Code
template_cancel = ["(1)" "AHP.BL.type (2)" ("AHP.BL.name (3a)" | "AHP.BL.ARP (3b)")  ] "\n" \n 
"Apron" "APN.BL.name" ["(4)" ("," | "and")] {"APN.BL.name" ["(4)" ("," | "and")]} ("resumed normal operations." | " : New NOTAM to follow.(8)").

The following pattern should be used for automatically generating the E field text from the AIXM data

Reference

Rule

(8)

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”. 

  • No labels