[APN.LIM] Apron - usage limitation change (NOTAM)

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;
- Note: According to encoding rule ER-02, the TEMPDELTA might also include ApronAreaAvailability elements that have been copied from the BASELINE data for compliance with the AIXM Temporality rules. The current practice is to not include such static information in the NOTAM text. Therefore, all ApronAreaAvailability that have operationalStatus='NORMAL' (they also have an associated annotation with purpose='REMARK' and the text="Baseline data copy. Not included in the NOTAM text generation") will be ignored for the NOTAM generation.

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 contain the AHP.BL.designator, if AHP.BL.locationIndicatorICAO='YES'. Otherwise, the nationality letter(s) as defined in ICAO Doc 7910 followed by “XX” or “XXX”.

Q code

The following mapping shall be used:

APN.TD.availability.ApronAreaAvailability.
timeInterval	usage.ApronAreaUsage					Corresponding Q Code
timeInterval	type	operation	priorPermission	../FlightCharacteristics	../AircraftCharacteristics	Corresponding Q Code
any	'FORBID'	any	any	any	weight not NIL	QMNLH
any other combination						QMNLT

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-readable 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 "APN.TD.usage.type(6)" (["APN.TD.usage.flight(7)"] ["APN.TD.usage.aircraft(8)"] ["APN.TD.usage.operation(9)"] ["conditions(10)"]) { "(11)" "," (["APN.TD.usage.flight(7)"] ["APN.TD.usage.aircraft(8)"] ["APN.TD.usage.operation(9)"] ["conditions(10)"])} \n
 
template_bottom =
["\n" "due to" "APN.TD.availability.annotation(12)"] "\n" \n
{"." "APN.TD.availability.annotation(13)" "\n"} ["."].

Reference

Data item (from coding scenario)

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)

airport name

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)

apron name

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)

conditional for

closed, except for

prohibited for

additionally allowed for

Insert here TD.availability.ManoeuvringAreaAvailability.usage.ManoeuvringAreaUsage as follows:

type	Text to be inserted in item E
"CONDITIONAL"	"available for"
"RESERV"	"closed, except for"
"PERMIT"	"now available for"
"FORBID"	"prohibited for"

(7)

flight

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)