Page Comparison

Note: this scenario corresponds to two NOTAM Templates:"Published PRD, TSA - area - activation” and “Published Navigation Warning Areas – activity”. Therefore, two item E production rules are included in this scenario.

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 BL. indicates that the corresponding data item must be taken from the Airspace BASELINE, which is valid at the start time of the Event;
the abbreviation TD. indicates that the corresponding data item must be taken from the Airspace TEMPDELTA that was created for the Event.

Important note: According to encoding rules for SAA.ACT, the TEMPDELTA might also include AirspaceActivation 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 AirspaceActivation that have an associated annotation with purpose=REMARK and the text="Baseline data copy. Not included in the NOTAM text generation" shall be excepted from the text NOTAM generation algorithm!

Several NOTAM possible

Note that if a special activity area is located in the vicinity of one or more airports or affects more than one FIR, there are special provision in the OPADD (v4.0, section 2.3.9.2) with regard to the NOTAM that need to be issued in order to ensure that the NOTAM appear correctly in the relevant en-route and airport Pre-Flight Information Bulletins (PIB).

...

The rules for the “first NOTAM” are indicated below, for any additional NOTAM with scope A, refer to “several NOTAM possible” section.

Item A

The Item A shall be generated according to the geographical location of the Airspace as follows:

if no AirportHeliport are predefined in the application as requiring a NOTAM during the activation of the area, then Item A shall contain the Airspace.designator of the predefined FIR(s) for which a NOTAM has to be issued;
if one or more airports are predefined in the application as requiring a NOTAM during the activation of the area, then each such NOTAM shall contain the AirportHeliport.locationIndicatorICAO of the predefined airports for which a NOTAM has to be issued.

if AirportHeliport.locationIndicatorICAO is empty, then CXXX or CCXX shall be used, where C/CC are the country code. In this case, the AirportHeliport.name shall be added at the beginning of Item E (see OPADD 2.3.14). Note that this element does not appear in the Item E pattern diagram further down.

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 first NOTAM (the values marked with an asterisk * are unlikely to occur in practice, they are provided for completeness sake and to prevent undefined situations for the automatic creation of NOTAM):

BL.type	TD.AirspaceActivation.activity (if not specified, refer to BL.AirspaceActivation.activity)	Corresponding Q code
P	any	QRPCA
R	any	QRRCA
D	any	QRDCA
TSA	any	QRRCA or QRTCA
TRA	any	QRRCA or QRTCA
W	any	QRMCA or QRDCA
MTR, OTHER:MOA	any	QRMCA
D-OTHER, A or OTHER	AERIAL_WORK, CROP_DUSTING, HI_RADIO*	QRDCA
D-OTHER, A or OTHER	none specified	QRDCA
D-OTHER, A or OTHER	AIRSHOW*	QWALW
D-OTHER, A or OTHER	SPORT*, AEROBATICS	QWBLW
D-OTHER, A or OTHER	EXERCISE, NAVAL_EXER, TRAINING, JET_CLIMBING	QWELW
D-OTHER, OTHER:AAR, A or OTHER	REFUEL	QWFLW
D-OTHER, A or OTHER	GLIDING	QWGLW
D-OTHER, A or OTHER	BLASTING, WATER_BLASTING	QWHLW
D-OTHER, A or OTHER	BALLOON, OTHER:HOT_AIR_BALLOON, OTHER:MET_BALLOON, OTHER:FREE_BALLOON, RADIOSONDE*	QWLLW
D-OTHER, A or OTHER	TOWING	QWJLW
D-OTHER, A or OTHER	MISSILES, OTHER:ROCKET_FIRING, OTHER:GUN_FIRING, AIR_GUN, ARTILLERY, SHOOTING, ANTI_HAIL, FIREWORK*, SPACE_FLIGHT	QWMLW
D-OTHER, A or OTHER	PARACHUTE, PARAGLIDER, HANGGLIDING, ULM*, AIR_DROP	QWPLW
D-OTHER, A or OTHER	CHEMICAL, NUCLEAR, REFINERY, TECHNICAL	QWRLW
D-OTHER, A or OTHER	GAS, OIL	QWSLW
D-OTHER, A or OTHER	UAV	QWULW
PROTECT	NATURE, FAUNA, NO_NOISE, ACCIDENT, POPULATION, VIP, VIP_PRES, VIP_VICE	QROLP
Any other combination of type and activity...		QXXXX or as decided by the operator

Notes:

In the situations where two or more Q code alternatives are provided in the table above, the first one should be used as default in a data provider interface. The operator shall have the possibility to select an alternative one or even to change it completely (for example, by using "XX").

Scope

As general rules, for each NOTAM that is generated:

...

However, more specific rules may be applied, depending on the split in NOTAM series, actual configuration of the FIR, etc. These have to be taken into consideration for each implementation.

Lower limit / Upper limit

For the first NOTAM, for activation with baseline limits, apply the common rules for {{Lower limit / Upper limit}}

...

Lower limit: use the lowest value between BL.AirspaceVolume.lowerLimit and TD.AirspaceActivation.AirspaceLayer.lowerLimit as basis for entry in lower limit of Q line.
Upper limit: use the highest value between BL.AirspaceVolume.upperLimit and TD.AirspaceActivation.AirspaceLayer.upperLimit as basis for entry in lower limit of Q line.

Geographical reference

For the first NOTAM, calculate the centre and the radius (in NM) of a circle that encompasses the whole special activity area. Insert these values in the geographical reference item, formatted as follows:

...

See also the Note with regard to the risk that the circle/radius does not encompass the whole area, as discussed in the {{Location and radius}} common rules for the NOTAM text generation.

Item B, C and D

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

If at least one TD.activation.AirspaceActivation.timeInterval exists (the Event has an associated schedule), then it 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

Two patterns are possible for automatically generating the E field text from the AIXM data:

Published PRD, TSA - area activation

This template shall be used when the BL.type has one of the values P, R, D, TSA, TRA, W.

...

Image Added

Published Navigation Warning Areas - activity

This template shall be used when the BL.type has a value different from P, R, D, TSA, TRA, W.

Image Modified

Reference

Rule

(1)

The area type shall be included according to the following decoding table:

BL.type	Text to be inserted in Item E
P	“Prohibited area”
R	"Restricted area"
D	"Danger area"
TSA	"Temporary segregated area"
TRA	"Temporary reserved area"
W	"Warning area"
MTR	“Military training route”
OTHER:MOA	“Military operations area”
OTHER:AAR	“Air-to-air refuelling area”

(2)

The designator and the name of the area shall be included if present in the BASELINE data.

(3)

The activation status code shall be translated into readable text, as follows:

ACTIVE => "activated"
IN_USE* => "in use"
INTERMITTENT => “activated (intermittent use)”

The values marked with an asterisk (*) are unlikely to occur in practice.

(4)

The activity code shall be translated into readable text, as indicated below. The values marked with an asterisk (*) are unlikely to occur in practice. However, a decoding is also provided for completeness sake.

ACCIDENT* => "flight accident site"
AERIAL_WORK* => "aerial work"
AEROBATICS => "aerobatics"
AIR_DROP => "air dropping"
AIR_GUN* => "firing in the air taking place"
AIRSHOW* => "air display"
ANTI_HAIL => "anti hail missiles launch"
ARTILLERY* => "artillery firing"
BALLOON => "ascent of balloon"
BIRD* => "bird presence"
BIRD_MIGRATION* => "bird migration"
BLASTING* => "explosives blasting"
CHEMICAL* => "chemical hazard"
CROP_DUSTING* => "crop spraying"
EXERCISE => "military exercise"
FAUNA* => "fauna protection"
FIRE_FIGHTING* => "fire fighting"
FIREWORKS* => "fireworks"
GAS* => "gas hazard"
GLIDING => "glider flying"
HANGGLIDING => "hang gliding"
HI_RADIO* => "high power radio transmissions"
JET_CLIMBING => "jet climbing"
LASER => "laser hazard"
MILOPS* => "military operations"
MISSILES => "missile firing"
NATURE* => "nature protection"
NAVAL_EXER => "naval exercise"
NO_NOISE* => "noise prevention reasons"
NUCLEAR* => "nuclear hazard"
OIL* => "oil hazard"
OTHER => "unspecified hazard"
OTHER:GUN_FIRING =>”gun firing”
OTHER:HOT_AIR_BALLOON => "hot air balloon”
OTHER:MET_BALLOON => "met balloon”
OTHER:FREE_BALLOON => "free balloon”
OTHER:ROCKET_FIRING => “rocket firing”
OTHER:LGT_OUT_NVG => “Lights out night vision goggle training”
PARACHUTE => "PJE"
PARAGLIDER => "paragliding"
POPULATION* => "population protection"
RADIOSONDE* => "radiosonde launching"
REFINERY* => "refinery hazard"
REFUEL => "air refuelling"
SHOOTING => "firing"
SPACE_FLIGHT* => "space flight"
SPORT* => "sport flights"
TECHNICAL* => "technical activities"
TOWING => "banner/target towing"
TRAINING => "training activities"
UAV => "unmanned acft system activities"
ULM => "ultralight motorized acft activities"
VIP* => "vip protection"
VIP_PRES* => "head of state protection"
VIP_VICE* => "vice-head of state protection"
WATER_BLASTING* => "water blasting"

(5)

If the TD.AirspaceActivation includes an AirspaceLayer that has:

upperLimit not equal to CEILING and different from any (if more than one present) BL.AirspaceGeometryComponent.upperLimit
or, lowerLimit not equal to FLOOR and different from any (if more than one present) BL.AirspaceGeometryComponent.lowerLimit

then the text "vertical limits changed during activation" or “vertical limits changed during activity”, as appropriate, shall be inserted here.

(6)

Annotations shall be translated into free text according to the common rules for annotations decoding.

Note: The objective is to full automatic generation of the NOTAM text, 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

The values to be inserted in Item F and G depend on the values of the TD.activation.AirspaceActivation.levels.

...

In all situations, the values in Items F and G shall be formatted according to common decoding rules for {{Item E, F, G - Vertical Limits}}.

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 some NOTAM C.

...

Two patterns are possible for automatically generating the E field text from the AIXM data:

Cancellation of Published PRD, TSA - area activation

This template shall be used when the BL.type has one of the values P, R, D, TSA, TRA, W.

Cancellation of Published Navigation Warning Areas - activity

This template shall be used when the BL.type has a value different from P, R, D, TSA, TRA, W.

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