Versions Compared

Version Old Version 3 New Version 4
Changes made by

Andreea Perca (Deactivated)

Andreea Perca (Deactivated)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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 APNAPE.BL. indicates that the corresponding data item must be taken from the Apron ApronElement BASELINE;

  • the abbreviation APEAPN.BL. indicates that the corresponding data item must be taken from the ApronElement BASELINEApron BASELINE where the ApronElement is located;

  • 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;the abbreviation APN.TD. indicates that the corresponding data item must be taken from the Apron TEMPDELTA that was created for the Event.


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.

...

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

Image RemovedImage Added

Code Block
titleEBNF Code
collapsetrue
template = ["(1)" "AHP.BL.type (2)" ("AHP.BL.name (3a)" | "AHP.BL.ARP (3b)")] \n "Acft standApron" "APN.BL.name" {"closed_apron_portion(4)"}["and(5)"| ","] {"Acft stand" "APN.BL.name" {"closed_apron_portion" ("between" "APE.BL.ElevatedSurface (4)"} ["and(5)"| ","]} \n "closed" [ "due to" "APN/APE.TD.availabilityBL.annotation (65)"]\n 
["(7)" "\n" "except"closed length" ["APN/APE.TDBL.usage.PPRlength(86)"] ["APN/APE.TD.usage.flight(9)"] ["APN/APE.TD.usage.aircraft(10)"] {"(11)" "," ["APN/APE.TD.usage.PPR(8)"] ["APN/APE.TD.usage.flight(9)"] ["APN/APE.TD.usage.aircraft(10)"]} ] "closed width" "APE.BL.width(7)") \n
["\n" "due to" "APE.BL.availability.annotation(8)"] \n
{"\n" "APN/APE.TD.availabilityBL.annotation(129)" "."} ["."].

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)Insert here
the APN.annotation and/or APE.annotation note with purpose
the list of coordinates of the apron portion closed geometry.
(5)Insert here the APE.annotation note with propertyName="extent" and 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
translated into free text according to the decoding rules for annotations. 
(6) Insert here the length of the closed portion followed by its unit of measurement decoded according to the {{text NOTAM production rules for distances}}
(7)Insert here the width of the closed portion followed by its unit of measurement decoded according to the {{text NOTAM production rules for distances}}
(8)Insert here the ApronElement/ApronAreaAvailability.annotation with propertyName="operationalStatus" and purpose="REMARK"
, then translate it
  translated into free text according to the
 
decoding rules for annotations. 

(

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

9)

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

...

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

Image RemovedImage Added

Code Block
titleEBNF Code
collapsetrue
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.(1310)"].


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

Reference

Rule

(1310)

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”