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.TD. indicates that the corresponding data item must be taken from the RunwayCentrelinePoint TEMPDELTA that has been created for the Event;
the abbreviation RCP.TD.RDD. indicates that the corresponding data item must be taken from the associatedDeclaredDistance.RunwayDeclaredDistance of the RunwayCentrelinePoint TEMPDELTA that has been created for the Event;
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;

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:

RCP.BL.role	Corresponding Q codes
'THR' or 'DISTHR'	QMTCM
any other value	QMDCH

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 shall be left empty. Note: If the declared distances are associated with a schedule, this information will be provided in item E, next to the group of declared distances concerned. This is a different approach from the current NOTAM practice where the NOTAM user is left to integrate the information that remains valid from the baseline (AIP) data with the values provided by NOTAM. In this scenario, the NOTAM generated automatically from the AIXM coded data includes all declared distances, not only the changed values.

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)")  ] ["unpaved (4)"] "RWY.BL.type(5)" "RDN.BL.designator" \n
["RCP.BL.role (6)"] ["RCP.BL.designator (7)"] ["8" "(" "RCP.TD.annotation" ")"]  "displaced" ["RCP.TD.annotation (9)"] \n
"," "position" "RCP.TD.ElevatedPoint (10)" ["," "elevation" "RCP.TD.ElevatedPoint.elevation (11)"]"." "\n" \n
["(12)" "(13)" "(14)" "RCP.TD.RDD.type(15)" "RCP.TD.RDD.declaredValue.RunwayDeclaredDistanceValue.distance(16)" {"(14)" "(14)" "RCP.TD.RDD.type(15)" "RCP.TD.RDD.declaredValue.RunwayDeclaredDistanceValue.distance(16)"} ["RCP.TD.RDD.declaredValue.RunwayDeclaredDistanceValue.timInterval.Timesheet(17)"] "\n" {"(13)" "(13)" "(14)" "RCP.TD.RDD.type(15)" "RCP.TD.RDD.declaredValue.RunwayDeclaredDistanceValue.distance(16)" {"(14)" "(14)" "RCP.TD.RDD.type(15)" "RCP.TD.RDD.declaredValue.RunwayDeclaredDistanceValue.distance(16)"} ["RCP.TD.RDD.declaredValue.RunwayDeclaredDistanceValue.timInterval.Timesheet(17)"] "\n"}] \n
["\n" "RCP.TD.annotation (18)" "."].

Reference

Data item (from coding scenario)

Rule

(1)

airport designator

If AHP.BL.locationIndicatorICAO is not null, 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

If AHP.BL.name is not NIL, then insert it here. Otherwise:
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)

runway surface composition

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)

Insert here the type of the Runway decoded as follows

RWY.BL.type	Text to be inserted in Item E
RWY	"RWY"
FATO	"FATO"

(6)

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

RCP.BL.role	Text to be inserted in Item E
THR	"THR"
DISTHR	"THR"
START_RUN	"Start of TKOF run"
other value	"centreline point"

(7)

centreline point designator

If RCP.BL.role is equal-to 'THR' or 'DISTHR', then ignore this element. Otherwise, if not null, insert the RCP.BL.designator.

(8)

centreline point location note

If the RCP.TD has an annotation.Note with propertyName equal to 'location' and purpose equal to 'REMARK', then translate it into free text according to the rule for annotations decoding

(9)

displacement distance

If the RCP.TD has an annotation.Note with propertyName equal to 'location' and purpose equal to 'DESCRIPTION', then translate it into free text according to the rule for annotations decoding

(10)

new position

Insert here the RCP.TD.location.ElevatedPoint decoded according to the text NOTAM production rules for aixm:Point. For resolution refer to ICAO Doc 10066, PANS-AIM, Appendix 1.

(11)

new elevation

If provided, insert here the RCP.TD.location.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

(12)

If there exist RCP.TD.RDD child elements, then use this branch. Otherwise ignore this branch.

(13)

schedule

If there exist RCP.TD.RDD.declaredValue.RunwayDeclaredDistanceValue.timInterval.Timesheet (there is a schedule applicable to certain declared distances), then group the RCP.TD.RDD.declaredValue.RunwayDeclaredDistanceValue by identical timeInterval.Timesheet. Otherwise (no schedule), create just one group.

(14)

For each group of RCP.TD.RDD.declaredValue.RunwayDeclaredDistanceValue selected in rule (#13), order them by parent RCP.TD.RDD.type (in the order 'TORA', 'TODA', 'ASDA', 'LDA', 'TODAH', 'RTOAH', 'LDAH', other values...) and process each of them as indicated

(15)

declared distance type

Insert here the declared distance type decoded as indicated below.

RCP.TD.RDD.type	Text to be inserted in Item E
TORA	"TORA"
TODA	"TODA"
ASDA	"ASDA"
LDA	“LDA”

RCP.TD.RDD.type	Text to be inserted in Item E
TODAH	"TODAH"
RTODAH	"RTODAH"
LDAH	"LDAH"

(16)

declared distance value

Insert here the declared distance value followed by its unit of measurement decoded according to the text NOTAM production rules for distances

(17)

schedule

Process the Timesheet of the group according to the NOTAM production rules for Item D, E - Schedules

(18)

note

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.BL.type (2)" ("AHP.BL.name (3a)" | "AHP.BL.ARP (3b)")  ]  ["unpaved(4)"] "RWY.BL.type(5)" "RDN.BL.designator" ("resumed normal operations." | " : New NOTAM to follow.(19)").

Reference	Rule
(19)	If the NOTAM will be followed by a new NOTAM concerning the same situation, then the operator shall have the possibility to choose the "New NOTAM to follow" branch. This branch cannot be selected automatically because this information is only known by the operator. Note: in this case, the 4th and 5th letters of the Q code shall also be changed into “XX”.

Reference

Rule

(19)

If the NOTAM will be followed by a new NOTAM concerning the same situation, then the operator shall have the possibility to choose the "New NOTAM to follow" branch. This branch cannot be selected automatically because this information is only known by the operator.

Note: in this case, the 4th and 5th letters of the Q code shall also be changed into “XX”.

Browser not supported