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 ASE.BL. indicates that the corresponding data item must be taken from the Airspace BASELINE that is created by the Event;
...
- if the Event has an associationEvent to an Airspace of type=FIR generate a NOTAM with scope W. If more of such Airspace feature(s) are identified, their identificator shall be listed in item A.
- if the Event has an associationEvent to an Airspace of type CTR or TMA, identify the AirportHeliport feature(s) that are located in those CTR/TMA and that also have locationIndicatorICAO="YES"; according to the OPADD rules, propose that a single NOTAM with scope AW and /or additional NOTAM with scope A are issued for these airports;
- if the Event has an associationEvent to an AirportHeliport that have their ARP located within 5 NM (configurable parameter) and have locationIndicatorICAO="YES", propose that a single NOTAM with scope AW and /or additional NOTAM with scope A are issued for these airports
The rules for the “first NOTAM” and the NOTAM containing one or more FIR in Item A are indicated below, for . For any additional NOTAM with scope A, refer to “several NOTAM possible” section.
...
The following mapping shall be used:
ASE.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 |
...
The following pattern should be used for automatically generating the E field text from the AIXM data:
(needs update)
| Code Block | ||||
|---|---|---|---|---|
| ||||
template = ("ASE.BL.type(1)" "ASE.BL.name(2)" ["ASE.BL.designator(3)" ["(" "class" "ASE.BL.classification" ")"] | "Class" "ASE.BL.classification(3)" "airspace" ["(" "ASE.BL.designator(3)" ")"] ["ASE.BL.name(2)") "established within:" "\n" \n
"ASE.BL.geometryComponent.horizontalProjection(5)" ["(" "ASE.BL.annotation(6)" ")"] "," \n "from" "ASE.BL.geometryComponent.lowerLimit(7)" "up to" "ASE.BL.geometryComponent.upperLimit(8)"
{"," "excluding" "ASE.BL.geometryComponent(9)"} "." \n
["\n" "Active as follows:" "ASE.BL.AirspaceActivation.timeInterval(10)" "."] \n
["\n" "ASE.BL.AirspaceActivation.annotation(11)" "."] \n
{"\n" "ASE.BL.annotation(12)" "."}. |
Reference | Rule | ||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
(1) | If ASE.BL.validTime.TimePeriod.endPosition is NIL and ASE.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:
| ||||||||||||||||||||||||||||||||||
(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. |
...