Versions Compared

Version Old Version 2 New Version 3
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

...

  • the abbreviation RDN.BL. indicates that the corresponding data item must be taken from the RunwayDirection BASELINE;

  • the abbreviation AHP.BL. indicates that the corresponding data item must be taken from the AirportHeliport BASELINE associated with the Runway that is associated with the RunwayDirection concerned;

  • the abbreviation RWY.BL. indicates that the corresponding data item must be taken from the Runway BASELINE associated with the RunwayDirection concerned;

  • the abbreviation RDN.TD. indicates that the corresponding data item must be taken from the RunwayDirection TEMPDELTA that was created for the Event.

    • Notes:

      1. According to encoding rule ER-01, each RunwayDirection of the Runway concerned by the closure will have a TEMPDELTA encoded. However, the closure information will be identical for all runway directions. Therefore, if not specified otherwise, the RDN.TD referred in the NOTAM production rules below shall be the one of the RunwayDirection with the lowest designator number;

      2. According to encoding rule ER-1002, the TEMPDELTA might also include ManoeuvringAreaAvailability 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 ManoeuvringAreaAvailability that have operationalStatus=NORMAL (they also have an associated annotation with purpose=REMARK and the text="Baseline data copy. Not included in the NOTAM text generation") shall will be excepted from ignored for the text NOTAM generation algorithm.

Item A

The item A shall contain the AHP.BL.designator if AHP.BL.locationIndicatorICAO='YES'. Otherwise, the nationality letter(s) as defined in ICAO Doc 7910 followed by “XX” or “XXX”. be generated according to the general production rules for item A using the Event.concernedAirportHeliport,

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:

...

RDN.TD.availability.ManoeuvringAreaAvailability.usage

Corresponding Q codes

none specified

QFPLC

a unique one, having AirportHeliportUsage.type=”PERMIT” and a descendant flight.FlightCharacteristic.military=”MIL”

QFPAM

at least one AirportHeliportUsage.type=”CONDITIONAL”

QFPAP

any other combination

QFPLT

Scope

Insert the value ‘A’.

Lower limit / Upper limit

Use “000/999”

Geographical reference

Insert the coordinate of the ARP (aerodrome reference point) of the airport (AHP.BL.ARP.ElevatedPoint), formatted as follows:

...

Reference

Rule

(1)

If AHP.BL.locationIndicatorICAO is not null, 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)

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

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

Insert the word “unpaved” if RWY.BL.SurfaceCharacteristics.composition has one of the values CLAY, CORAL, EARTH, GRASS, GRAVEL, ICE, LATERITE, MACADAM, SAND, SNOW, WATER, OTHER. Otherwise do not insert anything.

(5)

Insert here the type of the Runway decoded as follows

RWY.BL.type

Text to be inserted in Item E

RWY

"RWY"

FATO

"FATO"

(6)

If more than one RunwayDirection has a TEMPDELTA associated with the Event, then insert the designator of each additional RunwayDirection, preceded by "/", starting with the one with the lower designator number. In general, a runway has two landing directions but there may exist very rare situations with 3-4 landing directions.

(7)

If there exists a RDN.TD.availability.annotation having propertyName="operationalStatus" and purpose="REMARK", then translate it into free text according to the decoding rules for annotations.

(8)

If there exist one or more RDN.TD.availability.usage then decode them following this branch, in the following order of priorities:

  • TD.availability.usage that have operation="ALL"

  • TD.availability.usage that have type="PERMIT"

  • ... other situations ...

  • TD.availability.usage that have priorPermission which is not NIL shall be decoded last.

(9)

Decode here the 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"

(10)

If the RDN.TD.availability.usage.ManoeuvringAreaUsage includes values for priorPermission or selection, then decode them here as follows:

Code Block
titleEBNF Code
collapsetrue
template_condition = ["RDN.TD.usage.priorPermission(11)"] ["RDN.TD.usage.flight(12)"] ["RDN.TD.usage.aircraft(13)"] 
{"(14)" "," ["RDN.TD.usage.priorPermission(11)"] ["RDN.TD.usage.flight(12)"] ["RDN.TD.usage.aircraft(13)"]}.


(11)

If RDN.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 " "RDN.TD.usage.priorPermission(11.1)" ["RDN.TD.usage.annotation(11.2)"].


Reference

Rule

(11.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}}

(11.2)

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

(12)

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.

(13)

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.

(14)

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

(15)

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

...