Versions Compared

Version Old Version 5 New Version 6
Changes made by

Andreea Perca (Deactivated)

Andreea Perca (Deactivated)

Saved on

Key

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

...

  • If Item A contains the designator of one (or more) FIR, insert WE.
  • If Item A contains the ICAO code of an airport, insert AW AE for the first such NOTAM and value A for the rest of the NOTAM.

...

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

(needs update)

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

OTHER:FIZ

"Helicopter Traffic Zone"

OTHER:TIA

“Traffic Information Area"

OTHER:TIZ

"Traffic Information Zone"

"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.

...