...
...
...
...
...
...
...
...
...
...
...
This section provides rules for the automated production of the text NOTAM message items, based on the AIXM 5.1.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 APN.BL. indicates that the corresponding data item must be taken from the Apron BASELINE;
the abbreviation APN.TD. indicates that the corresponding data item must be taken from the Apron TEMPDELTA that was created for the Event.
the abbreviation AHP.BL. indicates that the corresponding data item must be taken from the AirportHeliport BASELINE associated with the Apron that is associated with the ApronElement concerned;
Note: According to encoding rule ER-02, the TEMPDELTA might also include ApronAreaAvailability 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 ApronAreaAvailability 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") will be ignored for the NOTAM generation.
In general, the ICAO DOC 8126 and the OPADD rules shall be followed. These have not been copied in this document in order to avoid duplication with those documents. Only instructions that are specific to the AIXM encoding of this event are stated here.
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”.
Q code
The following mapping shall be used:
...
APN.TD.availability.ApronAreaAvailability.
...
type
...
Scope
Insert the value ‘A’.
Lower limit / Upper limit
Use “000/999”
Geographical reference
Insert the coordinate of the ARP (AHP.BL.ARP.ElevatedPoint) of the airport, formatted as follows:
the set of coordinates comprises 11 characters rounded up or down to the nearest minute; i.e. Latitude (N/S) in 5 characters; Longitude (E/W) in 6 characters;
the radius value is “005”.
Items B, C and D
Items B and C shall be decoded following the common production rules.
If at least one APN.TD.availability.ApronAreaAvailability.timeInterval or APE.TD.availability.ApronAreaAvailability.timeInterval exists (i.e. the Event has an associated schedule), then all such Timesheet(s) shall be represented in item D according to the common NOTAM production rules for Item D, E - Schedules. Otherwise, item D shall be left empty.
Item E
...
Item A
The item A shall be generated according to the general production rules for item A using the Event.concernedAirportHeliport.
Item Q
Q code
The following mapping shall be used:
APN.TD.availability.ApronAreaAvailability | |||||
|---|---|---|---|---|---|
| timeInterval | usage.ApronAreaUsage | Corresponding Q Code | |||
type | priorPermission | ../FlightCharacteristics | ../AircraftCharacteristics | ||
| any | 'FORBID' | any | any | weight not NIL | QMNLH |
| any other combination | QMNLT | ||||
Scope
Insert the value ‘A’.
Lower limit / Upper limit
Use “000/999”
Geographical reference
Insert the coordinate of the ARP (AHP.BL.ARP.ElevatedPoint) of the airport, formatted as follows:
the set of coordinates comprises 11 characters rounded up or down to the nearest minute; i.e. Latitude (N/S) in 5 characters; Longitude (E/W) in 6 characters;
the radius value is “005”.
Items B, C and D
Items B and C shall be decoded following the common production rules.
If at least one APN.TD.availability.ApronAreaAvailability.timeInterval or APE.TD.availability.ApronAreaAvailability.timeInterval exists (i.e. the Event has an associated schedule), then all such Timesheet(s) shall be represented in item D according to the common NOTAM production rules for Item D, E - Schedules. Otherwise, item D shall be left empty.
Item E
The following pattern should be used as a base for generating the E field text from the AIXM data:
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
template = ["(1)" "AHP.BL.type (2)" ("AHP.BL.name (3a)" | "AHP.BL.ARP (3b)")] \n "Apron (4)" "APN.BL.name" ["(5)" ("," | "and")] {"APN.BL.name" ["(5)" ("," | "and")]}
\n "APN.TD.usage.type(6)" (["APN.TD.usage.flight(7)"] ["APN.TD.usage.aircraft(8)"] [" |
...
conditions(9)"] |
...
) |
...
{ "( |
...
10)" " |
...
," (["APN.TD.usage. |
...
flight( |
...
7)"] ["APN.TD.usage. |
...
aircraft( |
...
8)"] ["conditions( |
...
9)"])} |
...
. template_bottom = ["\n" "due to" "APN.TD.availability.annotation( |
...
11)"] "\n" \n {"." "APN.TD.availability.annotation( |
...
12)" "\n"} ["."]. |
Reference | Data item (from coding scenario) | Rule |
|---|---|---|
(1) | If AHP.BL.locationIndicatorICAO |
...
is not null, then ignore this branch. | ||||||||||
(2) | Insert here the type of the airport decoded as follows
| |||||||||
(3) | airport name | (a |
...
) If AHP.BL.name is not |
...
null, then insert it here. (b) Otherwise, |
...
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) |
...
| For the potential applications/implementations - the word " |
...
| Apron" may appear twice depending on the coded APN.BL.name (e.g. |
...
| Apron MILITARY APRON or |
...
| Apron APRON A1). Caution shall be exercised for NOTAM production to avoid possible duplications. | ||
(5) | apron name | If more than one |
...
Apron has a TEMPDELTA associated with the Event, then insert the designator of each additional apron designator preceded by ",". Insert "and" before the last entry. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| (6) | conditional for closed, except for prohibited for additionally allowed for | Insert hereTD.availability.ManoeuvringAreaAvailability.usage.ManoeuvringAreaUsage as follows:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
(7) | 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.
*Note: type is unlikely to be used in a NOTAM, its decoding is provided for completeness sake.
*Note: value is unlikely to be used in a NOTAM, its decoding is provided for completeness sake.
*Note: value is unlikely to be used in a NOTAM, its decoding is provided for completeness sake.
*Note: value is unlikely to be used in a NOTAM, its decoding is provided for completeness sake.
*Note: value is unlikely to be used in a NOTAM, its decoding is provided for completeness sake. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
(8) | 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.
|
...
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
...
|
...
*Note: |
...
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:
...
value is unlikely to be used in a NOTAM, its decoding is provided for completeness sake.
|
...
|
...
BELOW
...
|
...
AT_OR_ABOVE
...
"acft with wingspan equal to or more than"
...
AT_OR_BELOW
...
“acft with wingspan equal to or less than"
|
...
**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:
|
...
|
...
|
...
|
...
|
...
|
...
|
...
Decode here the APN.TD.availability.usage.operation as follows:
...
*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:
|
...
|
...
|
...
ALL**
...
"for all operations"**
...
CROSSING
...
"for crossing"
...
LANDING*
...
"for landing"
...
TAKEOFF*
...
"for tkof”
...
TAXIING
...
"for taxiing"
...
TOUCHGO*
...
"for tgl"
...
TRAIN_APPROACH*
...
*Note: value is unlikely to be used in a NOTAM, its decoding is provided for completeness sake |
...
. |
| ( |
...
| 9 | 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: |
...
|
...
Reference
...
Rule
...
(10.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}}
...
|
...
|
...
| |
( |
...
10) | If there exists a parent APN.TD.availability.ApronAreaAvailability.usage.ApronAreaUsage.selection.ConditionCombination with logicalOperator='OR' (there are more than one flight/aircraft combinations that are excepted), then select and decode each |
...
child subCondition.ConditionCombination/... consecutively and insert the comma separator. |
| ( |
...
| 11) | If there exists a APN.TD.availability.annotation having propertyName= |
...
| 'operationalStatus |
...
| ' and purpose='REMARK', then translate it into free text according to the decoding rules for annotations. |
( |
...
12) | Annotations of APN.TD.ApronAreaAvailability shall |
...
be translated into free text according to the decoding rules for annotations. |
Note: The objective is to full automatic generation, without human intervention. However, the implementers of the specification might consider reducing the cost of a fully automated generation by allowing the operator to fine-tune the text in order to improve its readability (with the inherent risk for human error, when re-typing is allowed).
Items F & G
Leave empty.
Event Update
The eventual update of this type of event shall be encoded following the general rules for
...
Event update or cancellation, which provide instructions for all NOTAM fields, except for item E and the condition part of the Q code, in the case of a NOTAMC
If a NOTAMC is produced, then the 4th and 5th letters (the "condition") of the Q code shall be "AK", except for the situation of a “new NOTAM to follow", in which case “XX”shall be used.
The following pattern should be used for automatically generating the E field text from the AIXM data.
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
template_cancel = ["(1)" "AHP.BL.type (2)" ("AHP.BL.name (3a)" | "AHP.BL.ARP (3b)") ] "\n" \n
"Apron" "APN.BL.name" ["(5)" ("," | "and")] {"APN.BL.name" ["(5)" ("," | "and")]} ("resumed normal operations." | " : New NOTAM to follow.( |
...
13)"). |
The following pattern should be used for automatically generating the E field text from the AIXM data
Reference | Rule |
( |
...
13) | If the NOTAM will be followed by a new NOTAM concerning the same situation, then the operator shall have the possibility to choose the "New NOTAM to follow" branch. This branch cannot be selected automatically because this information is only known by the operator. Note: in this case, the 4th and 5th letters of the Q code shall also be changed into “XX”. |