Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

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 TWY.BL. indicates that the corresponding data item must be taken from the Taxiway BASELINE;
  • the abbreviation TWY.TD. indicates that the corresponding data item must be taken from the Taxiway TEMPDELTA that was created for the Event in case of complete taxiway closure;
  • the abbreviation TWE.TD. indicates that the corresponding data item must be taken from the TaxiwayElement TEMPDELTA that was created for the Event in case of taxiway portion closure;
  • the abbreviation AHP.BL. indicates that the corresponding data item must be taken from the AirportHeliport BASELINE associated with the Taxiway that is associated with the TaxiwayElement 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

The following mapping shall be used:

TWY.BL.type

Corresponding Q codes

if other than FASTEXIT

QMXLC

FASTEXIT

QMYLC

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 TWY.TD.availability.ManouevringAreaAvailability.timeInterval or TWE.TD.availability.ManouevringAreaAvailability.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

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 ("Rapid exit TWY(4)" | "TWY") "TWY.BL.designator(5)" {"closed_taxiway_portion(6)"}["and(7)"| ","] {("Rapid exit TWY(4)" | "TWY") "TWY.BL.designator(5)" {"closed_taxiway_portion(6)"} ["and(7)"| ","]}
\n "closed" [ "due to" "TWY/TWE.TD.availability.annotation (8)"]\n 
{"\n" "TWY/TWE.TD.availability.annotation(9)" "."} ["."].

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)

if TWY.BL.type = FASTEXIT insert the words “Rapid exit". Otherwise insert "TWY".

(5)

If more than one Taxiway and/or TaxiwayElement has a TEMPDELTA associated with the Event, then insert the designator of each additional Taxiway, designator preceded by ",". Insert "and" before the last entry. 

(6)

Insert here the TWY.annotation and/or TWE.annotation note with purpose="OTHER:DESCRIPTION" stored in the BASELINE data (e.g. “between TWY A and TWY B”).

If taxiway elements are used, the automatic generation of an easy human-readeable NOTAM text is practically impossible using just the AIXM encoding. Two cases can be identified for describing the closed taxiway portion:

Case 1: use long text from descriptions, as available in the TWE.annotation. 

Example: Following the example of Fig.1 from coding rules, the text would look as follows: "between TWY B and TWY C, intersection TWY A and TWY C, between TWY C and TWY D” 

Case 2: allow the operator to manually write the text part. 

Since the operator is allowed to modify the item E text manually, the choice to simplify the text can be made. The result of manual editing could result in something as follows: "between TWY B and TWY D, including intersections between".

(7) Insert "and" before the last taxiway or taxiway portion affected by the closure (e.g. "TWY A, TWY B and TWY C") 

(8)

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

(9)

Annotations of TD.ManoeuvringAreaAvailability 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 {{Event updates 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.

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

EBNF Code 
template_cancel = ["(1)" "AHP.BL.type (2)" ("AHP.BL.name (3a)" | "AHP.BL.ARP (3b)")  ] "\n" \n ("Rapid exit TWY(4)" | "TWY") "TWY.BL.name" {("," | "and(5)") ("Rapid exit TWY(4)" | "TWY") "TWY.BL.name"} "resumed normal operations." ["New NOTAM to follow.(10)"].

Reference

Rule

(10)

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”

  • No labels