Versions Compared

Version Old Version 3 New Version 4
Changes made by

Andreea Perca (Deactivated)

Andreea Perca (Deactivated)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • if no airport NOTAM are issued, then item A shall contain the Airspace.designator of the FIR(s) for which the NOTAM is issued;
  • if one or more airports NOTAM are issued, then each such NOTAM shall contain the AirportHeliport.locationIndicatorCAO of the airports for which the NOTAM is 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 Ed 4.0 paragraph 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:

...

The following mapping shall be used:

BL.type values

Corresponding Q codes

CTR

QACCA

ADIZ

QADCA

CTA

QAECA

UTA

QAHCA

OCA

QOACA

AWY

QARCA

TMA

QATCA

ADV

QAVCA

UDAV

QAVCA

ATZ

QAZCS

FIR

QAFCA

any other

QXXCA

Notes:


  • the operator shall have the possibility to change the Q code completely (for example, by using "XX").

...

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

Image Added

Reference

Rule

(1)

If BL.validTime.TimePeriod.endPosition is NIL and BL.validTime.TimePeriod.endPosition@indeterminatePosition has the value "unknown" (the area is permanent), then insert the word "PERMANENT".

(2)

If BL.type does not have the value "CLASS", then use this branch. Otherwise use the other branch, which inserts just the airspace classification.

(3)

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

BL.type

Text to be inserted in Item E

CTR

"CTR"

ADIZ

"ADIZ"

CTA

"CTA"

UTA

"UTA"

OCA

“OCA”

AWY

"AWY"

SECTOR

"ATS sector"

SECTOR_C

"collapsed ATS sector"

RAS

"regulated ATS airspace"

TMA

"TMA"

ADV

"Advisory Area"

UDAV

"Upper Advisory Area"

ATZ

"ATZ"

HTZ

"Helicopter Traffic Zone"

OTHER:TIA

“Traffic Information Area"

OTHER:TIZ

"Traffic Information Zone"

OTHER:FIZ

"Flight Information Zone"

FIR

“FIR” 

any other

"area"

(4)

If specified, insert here the BL.designator

(5)

If specified, insert here the BL.name

(6)

If specified, insert here only the BL.annotation that has propertyName="geometryComponent", which represents the encoding of the "location note" information. Annotations shall be translated into free text according to the decoding rules for annotations.

(7)

The GML encoding of the horizontalProjection (gml:Surface) (that is part of a BL.geometryComponent with operation="BASE" or not specified), shall be translated into human readable text, using latitude/longitude values.

(8)

Decode the BL.geometryComponent.lowerLimit/upperLimit (that is part of a BL.geometryComponent with operation="BASE" or not specified), including reference and unit of measurement, according to the decoding rules for vertical limits

(9)

If specified as a BL.geometryComponent with operation="SUBTR", insert here the designator and the type of the BL.geometryComponent.contributorAirspace. This requires interpreting the xlink:href value in order to recuperate the relevant data from the contributorAirspace BASELINE. If more than one airspace is excluded from the preceding horizontalProjection, then the word "AND" shall be included before the second, third, etc. exclusion.

(10)

If at least one BL.activation.AirspaceActivation.timeInterval exists (the Event has an associated schedule), then it shall be inserted here according to the general NOTAM conversion rules for Event schedules. Attention: timeInterval(s) that appear as child of BL.activation.AirspaceActivation with status=INACTIVE shall not be translated (because this was created for the completeness of the digital data encoding, see rule ER-05

(11)

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

Items F & G

Items F and G shall be left empty. The vertical limits are part of item E.

...

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

Image Added

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”