Page Comparison

Text NOTAM production rules

This section provides rules for the automated production of the text NOTAM message items, based on the AIXM 5.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 RSG.BL. indicates that the corresponding data item must be taken from the RouteSegment BASELINE which is valid at the start time of the Event;
• the abbreviation RSG.TD. indicates that the corresponding data item must be taken from the RouteSegment TEMPDELTA that was created for the Event;
• Note: According to encoding rule ER-08, the TEMPDELTA might also include RouteAvailability elements that have been copied from the BASELINE data for compliance with the AIXM Temporality rules. For RTE.OPN scenario such static information shall be included in the text NOTAM generation algorithm to assure clarity with respect to the route status. 

Item A

Identify the FIR(s) within which the RouteSegments concerned by the Event are located.

Item Q

Apply the common NOTAM production rules for item Q, complemented by the following specific rules for this particular scenario:

Q code

The following mapping shall be used for the Q code:

Scope

Insert the value ‘E’.

Lower limit / Upper limit

• the lowest value between all RSG.TD.RouteAvailability/AirspaceLayer.lowerLimit associated with the Event, formatted according to the common rules for {{Lower limit / Upper limit}}, shall be used as Lower limit;
• the highest value between all RSG.TD.RouteAvailability/AirspaceLayer.upperLimit associated with the Event, formatted according to the common rules for {{Lower limit / Upper limit}}, shall be used as Upper limit.

Geographical reference

Calculate the centre and the radius (in NM) of a circle that encompasses all route segments concerned. Insert these values in the geographical reference item, 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 consists of 3 figures rounded up to the next higher whole Nautical Mile; e.g. 10.2NM shall be indicated as 011.

Items B, C and D

Items B and C shall be decoded following the common production rules.

...

• only the closure schedules will be translated in the NOTAM Text. Eventual opening times described as schedules are considered as having been copied from the BASELINE, for completeness sake (see ER-06);
• according to the input template, a single set of schedules is applicable to all RouteSegment closures associated with the Event. This will be ensured with a data verification rule. Therefore, it is sufficient to decode the schedules associated with one of the RSG.TD.RouteAvailability.timeInterval.

Item E

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

...

Note: The objective is to full automatic 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

According to the OPADD rules, item F & G shall be left 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 NOTAM C

...