Versions Compared

Version Old Version 6 New Version 7
Changes made by

WOJTOWICZ Aleksander

WOJTOWICZ Aleksander

Saved on

Key

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

Text NOTAM production rules

...

Reference

Data item (from coding scenario)

Rule

(1)


If AHP.BL.locationIndicatorICAO='YES', 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

a. If AHP.BL.name is not NIL, then insert it here. Otherwise,

b. 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)


if TWY.BL.type = 'FASTEXIT' insert the words “Rapid exit". Otherwise, insert "TWY".

(5)

taxiway designator

If more than one Taxiway and/or TaxiwayElement has a TEMPDELTA associated with the Event, then insert the designator of each additional Taxiway, designator preceded by ",". Insert "and" before the last entry. 

(6)

closed taxiway portion input

Insert here the TWY.annotation and/or TWE.annotation note with purpose='OTHER:DESCRIPTION' stored in the BASELINE data (e.g. “between TWY A and TWY B”).

If taxiway elements are used, the automatic generation of an easy human-readable NOTAM text is practically impossible using just the AIXM encoding. Two cases can be identified for describing the taxiway portion affected by the limitation:

Case 1: use long text from descriptions, as available in the TWE.annotation. 

Example: Following the example of Fig.1 from coding rules, the text would look as follows: "between TWY B and TWY C, intersection TWY A and TWY C, between TWY C and TWY D” 

Case 2: allow the operator to manually write the text part. 

Since the operator is allowed to modify the item E text manually, the choice to simplify the text can be made. The result of manual editing could result in something as follows: "between TWY B and TWY D, including intersections between".

(7) 
Insert "and" before the last taxiway or taxiway portion affected by the limitation (e.g. "TWY A, TWY B and TWY C") 

(8)

conditional for

closed, except for

prohibited for

additionally allowed for

Insert here TWY/TWE.TD.availability.ManoeuvringAreaAvailability.usage.ManoeuvringAreaUsage as follows:

typeText to be inserted in item E
"CONDITIONAL""available for"
"RESERV""closed, except for"
"PERMIT""now available for"
"FORBID""prohibited for"

(9)

flight

Decode here each FlightCharacteristics property that was specified, as detailed below. If more than one FlightCharacteristics property was used, insert blanks between consecutive properties.

FlightCharacteristics.type*

Text to be inserted in Item E

OAT

"Operational Air Traffic"

GAT

"General Air Traffic"

ALL

"Operational Air Traffic/General Air Traffic"

OTHER:MY_TEXT

"my text" (replace "_" with blanks)

*Note: type is unlikely to be used in a NOTAM, its decoding is provided for completeness sake.


FlightCharacteristics.rule

Text to be inserted in Item E

IFR

"IFR"

VFR

"VFR"

ALL*

"IFR/VFR"

OTHER:MY_TEXT

"my text" (replace "_" with blanks)

*Note: value is unlikely to be used in a NOTAM, its decoding is provided for completeness sake.


FlightCharacteristics.status

Text to be inserted

HEAD

"Head of State"

STATE

"State acft"

HUM

"HUM"

HOSP

"HOSP"

SAR

"SAR”

EMERGENCY

"EMERG"

ALL

"State acft/HUM/HOSP/SAR/EMERG"

OTHER:MEDEVAC

“MEDEVAC”

OTHER:FIRE_FIGHTING

“fire fighting”

OTHER:MY_TEXT

"my text" (replace "_" with blanks and convert to lowercase)

FlightCharacteristics.military

Text to be inserted in Item E

MIL

"MIL acft"

CIVIL

"civil acft"

ALL*

"civil/MIL acft"

OTHER:MY_TEXT*

"my text" (replace "_" with blanks)

*Note: value is unlikely to be used in a NOTAM, its decoding is provided for completeness sake.


FlightCharacteristics.origin

Text to be inserted

NTL

"domestic"

INTL

"intl"

HOME_BASED

"home based"

ALL*

"domestic/intl"

OTHER:MY_TEXT*

"my text" (replace "_" with blanks)

*Note: value is unlikely to be used in a NOTAM, its decoding is provided for completeness sake.


FlightCharacteristics.purpose

Text to be inserted

SCHEDULED

"scheduled"

NON_SCHEDULED

"not scheduled"

PRIVATE*

"private"

AIR_TRAINING

"training"

AIR_WORK*

"aerial work"

PARTICIPANT

"participating acft"

ALL*

"scheduled/not scheduled/private/training/aerial work/participating acft"

OTHER:MY_TEXT*

"my text" (replace "_" with blanks)

*Note: value is unlikely to be used in a NOTAM, its decoding is provided for completeness sake.

(10)

aircraft

Decode here each AircraftCharacteristics property that was specified, as detailed below. If more than one AircraftCharacteristics property was used, insert blanks between consecutive properties.

AircraftCharacteristics.type

Text to be inserted in Item E

LANDPLANE

"landplanes"

SEAPLANE*

"seaplanes"

AMPHIBIAN

"amphibians"

HELICOPTER

"hel"

GYROCOPTER

"gyrocopters"

TILT_WING

"tilt wing acft"

STOL

"short take-off and landing acft"

GLIDER*

"gliders"

HANGGLIDER*

"hang-gliders"

PARAGLIDER*

"paragliders"

ULTRA_LIGHT*

"ultra lights"

BALLOON*

"balloons"

UAV*

"unmanned acft”

ALL*

"all acft types"

OTHER:MY_TEXT

"my text" (replace "_" with blanks)

*Note: value is unlikely to be used in a NOTAM, its decoding is provided for completeness sake.


AircraftCharacteristics.engine

Text to be inserted in Item E

JET

"jet acft"

PISTON

"piston acft"

TURBOPROP

"turboprop acft"

ELECTRIC**

“electric engine acft”

ALL

"all engine types"

OTHER:MY_TEXT

"my text" (replace "_" with blanks)

**Note: new in AIXM 5.1.1.


AircraftCharacteristics.wingSpan - insert the value followed by the value of the uom attribute. Prefix with the value of AircraftCharacteristics.wingSpanInterpretation, decoded as indicated in the following table:

AircraftCharacteristics.wingSpanInterpretation

Text to be inserted in Item E

ABOVE

"acft with wingspan more than"

AT_OR_ABOVE

"acft with wingspan equal to or more than"

AT_OR_BELOW

“acft with wingspan equal to or less than"

BELOW

"acft with wingspan less than"

OTHER:MY_TEXT*

"my text" (replace "_" with blanks)

*Note: value is unlikely to be used in a NOTAM, its decoding is provided for completeness sake.


AircraftCharacteristics.weight - insert the value followed by the value of the uom attribute. Prefix with the value of AircraftCharacteristics.weightInterpretation, decoded as indicated in the following table:

AircraftCharacteristics.weightInterpretation

Text to be inserted in Item E

ABOVE

"acft mass heavier than"

AT_OR_ABOVE

"acft mass equal to or heavier than"

AT_OR_BELOW

"acft mass equal to or lighter than"

BELOW

"acft mass lighter than"

OTHER:MY_TEXT*

"my text" (replace "_" with blanks)

*Note: value is unlikely to be used in a NOTAM, its decoding is provided for completeness sake.

(11)

operation

Decode here the TWY/TWE.TD.availability.usage.operation as follows:

TD.usage.operation*

Text to be inserted in Item E

LANDING*

"for landing"

TAKEOFF*

"for tkof”

TOUCHGO*

"for tgl"

TRAIN_APPROACH*

"for practice low approaches"

TAXIING

"for taxiing"

CROSSING

"for crossing"

AIRSHOW

"for acft participating in air display”

ALL**

"for all operations"**

*Note: value is unlikely to be used in a NOTAM referring to the taxiway limitation, its decoding is provided for completeness sake.

**Note: if all operations are affected, then either provide the text as described above or do not provide the text at all.

(12)

PPR time 

PPR details

If TD.usage.priorPermission is not NIL, then insert here the decoding of the PPR information as detailed in the following diagram:

Code Block
titleEBNF Code
collapsetrue
template_PPR = "PPR " "TWY/TWE.TD.usage.priorPermission(12.1)" ["TWY/TWE.TD.usage.annotation(12.2)"].

Reference

Rule

(12.1)

Insert here the value of the priorPermission attribute followed by its unit of measurement decoded according to the {{text NOTAM production rules for duration}}

(12.2)

Decode here the annotation with propertyName="priorPermission" and purpose="REMARK", according to the decoding rules for annotations.

(13)


If TD.usage.selection.logicalOperator=OR (there are more than one flight/aircraft combinations that are excepted), then select and decode each FlightCharacteristics/AircraftCharacteristics consecutively.

(14)reasonIf there exists a TWY.TD.availability.annotation or TWE.TD.availability.annotation having propertyName="operationalStatus" and purpose='REMARK', then translate it into free text according to the decoding rules for annotations.

(15)

note

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

...