Page tree
Skip to end of metadata
Go to start of metadata

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 RCP.BL. indicates that the corresponding data item must be taken from the RunwayCentrelinePoint BASELINE;
  • the abbreviation RDN.BL. indicates that the corresponding data item must be taken from the RunwayDirection BASELINE;
  • the abbreviation RWY.BL. indicates that the corresponding data item must be taken from the Runway BASELINE associated with the RunwayDirection concerned;
  • the abbreviation AHP.BL. indicates that the corresponding data item must be taken from the AirportHeliport BASELINE associated with the Runway that is associated with the RunwayDirection concerned;
  • the abbreviation RCP.TD. indicates that the corresponding data item must be taken from the RunwayCentrelinePoint TEMPDELTA that was created for the Event;
  • the abbreviation RCP.BL[n]. indicates that the corresponding data item must be taken from the new RunwayCentrelinePoint BASELINE that was created for the Event under encoding rule ER-04;

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:

Runway Centreline Point displaced

Corresponding Q codes

Threshold Displaced

QMTCM

Start of take-off run displacedQMRCH
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.

Item D is always empty.

Item E

The following pattern should be used for automatically 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" \n
["unpaved (4)"] (["RCP.BL.role (5)"] ["RCP.BL.designator"] | "(6)") "RWY" "RDN.BL.designator" "displaced" \n 
["RCP.TD.annotation (7)" "inwards"] \n
["," "position" "RCP.TD.ElevatedPoint (8)"]  \n 
["," "elevation" "RCP.TD.ElevatedPoint.elevation (9)"]"." "\n" \n
["Start of tkof run unchanged (10)"] "\n" \n
["RCP.TD.annotation (11)" "."].

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)

  1. If AHP.BL.name is not NIL, then insert it here. Otherwise:

  2. 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 the word “unpaved” if RWY.BL.SurfaceCharacteristics.composition has one of the values CLAY, CORAL, EARTH, GRASS, GRAVEL, ICE, LATERITE, MACADAM, SAND, SNOW, WATER, OTHER. Otherwise do not insert anything.

(5)

If RCP.BL.role is provided, insert here the runway centreline point role decoded as follows:

RCP.BL.roleText to be inserted in Item E
THR"THR"
DISTHR"THR"
START_RUN"Start of tkof run"

(legacy coding case) If there is a RCP.BL[n] and the RCP.BL[n].location/ElevatedPoint.pos is the same as the RCP.TD.location/ElevatedPoint.pos then insert here in continuation of the above, the following text "and Start of tkof run".

(6)If both RCP.BL.role and RCP.BL.designator are not provided, insert here "centreline point previously located at" followed by RCP.BL.location decoded according to the {{text NOTAM production rules for aixm:Point}}.

(7)

If provided, insert here the value from the LinguisticNote.note of RCP.TD.annotation with propertyName="distance" and purpose="DESCRIPTION".

(8)

If provided, insert here the RCP.TD.ElevatedPoint position decoded according to the {{text NOTAM production rules for aixm:Point}}. For resolution refer to ICAO Doc 10066, PANS-AIM, Appendix 1.

(9)

If provided, insert here the RCP.TD.ElevatedPoint elevation followed by its unit of measurement decoded according to the {{text NOTAM production rules for distances}}. For resolution refer to ICAO Doc 10066, PANS-AIM, Appendix 1

(10)(legacy coding case) If there is a RCP.BL[n] and the RCP.BL[n].location/ElevatedPoint.pos is the same as the RCP.BL.location/ElevatedPoint.pos then insert here "Start of tkof run unchanged.".

(11)

Annotations shall be translated into free text according to the rule for {{decoding annotations}}.

Note: The objective is to fully automate generation, without human intervention. However, the implementers of the specification might consider reducing the cost of a fully automated generation by allowing the operator to fine-tune the text in order to improve its readability (with the inherent risk for human error when re-typing is allowed).

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" unless there is a new NOTAM to follow, in which case the Q code shall be “XX” and the following pattern should be used for automatically generating the E field text from the AIXM data:

EBNF Code
template_cancel = ["(1)" "AHP.BLtype (2)" ("AHP.BL.name (3a)" | "AHP.BL.ARP (3b)")  ]"\n" \n
["unpaved (4)] "RWY" "RDN.BL.designator" "resumed normal operations." "\n" \n
["New NOTAM to follow (11)."].


Reference

Rule

(12)

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