Decoding

Text NOTAM production rules

...

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

In general, the ICAO DOC 8126 and the OPADD rules 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

title	EBNF Code
collapse	true

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)" ("," | ",and")] {"Acft stand" "APN.BL.name" {"closed_apron_portion ["(4)"} ["and(5)"("," | ",and")]}
\n "closed" [ "due to" "APN/APE.TD.availability.annotation (65)"]\n 
["(76)" "\n" "except" ["APN/APE.TD.usage.PPR(87)"] ["APN/APE.TD.usage.flight(98)"] ["APN/APE.TD.usage.aircraft(109)"] {"(1110)" "," ["APN/APE.TD.usage.PPR(87)"] ["APN/APE.TD.usage.flight(98)"] ["APN/APE.TD.usage.aircraft(109)"]} ] \n
{"\n" "APN/APE.TD.availability.annotation(1211)" "."} ["."].

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

Insert here the APN

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)

.

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

(4)

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.

(65)

If there exists a APN.TD.availability.annotation or APE.TD.availability.annotation having having propertyName="operationalStatus" and purpose="REMARK", then translate it into free text according to the decoding rules for annotations.

(76)

If there exist one or more TD.availability.usage then decode them following this branch, in the following order of priorities:

TD.availability.usage that have operation="ALL"
TD.availability.usage that have type="PERMIT"
... other situations ...
TD.availability.usage that have priorPermission which is not NIL shall be decoded last.

(87)

If TD.usage.priorPermission is not NIL, then insert here the decoding of the PPR information as detailed in the following diagram:

Image RemovedImage Added

Code Block

title	EBNF Code
collapse	true

template_PPR = "PPR " "TWY/TWE.TD.usage.priorPermission(87.1)" ["TWY/TWE.TD.usage.annotation(87.2)"].

Reference	Rule
(87.1)	Insert here the value of the priorPermission attribute followed by its unit of measurement decoded according to the {{text NOTAM production rules for duration}}
(87.2)	Decode here the annotation with propertyName="priorPermission" and purpose="REMARK", according to the decoding rules for annotations.

(98)

Decode here each FlightCharacteristics property that was specified, as detailed below. If more than one FlightCharacteristics property was used, insert blanks between consecutive properties.

FlightCharacteristics.type*	Text to be inserted in Item E
OAT	"Operational Air Traffic"
GAT	"General Air Traffic"
ALL	"Operational Air Traffic/General Air Traffic"
OTHER:MY_TEXT	"my text" (replace "_" with blanks)

*Note: type is unlikely to be used in a NOTAM, its decoding is provided for completeness sake.

FlightCharacteristics.rule	Text to be inserted in Item E
IFR	"IFR"
VFR	"VFR"
ALL*	"IFR/VFR"
OTHER:MY_TEXT	"my text" (replace "_" with blanks)