...
...
...
...
...
...
Item A
The item A shall
...
Q code
The following mapping shall be used:
...
Availability.usage
...
Corresponding Q codes
...
none specified
...
QMNLC
...
there exist associated ApronAreaUsage.type PERMIT or CONDITIONAL
...
QMNLT
...
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
Insert QMNLC
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
...
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:
old:
new:
| 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 "closed" [ "due to" "APN.TD.availability.annotation (6)"] |
...
\n |
...
|
...
{" |
...
\n" "APN.TD.availability.annotation( |
...
7)" "."} ["."]. |
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) | (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) | closure reason | If there exists a APN.TD.availability.ApronAreaAvailability.annotation having propertyName= |
...
'operationalStatus |
...
' and purpose= |
...
'REMARK |
...
(10)
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)
...
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.
...
(12)
...
', then translate it into free text according to the decoding rules for annotations. |
(7) |
...
If there exist one or more 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.
...
If TD.usage.priorPermission is not NIL, then insert here the decoding of the PPR information as detailed in the following diagram:
| Code Block | ||||
|---|---|---|---|---|
| ||||
template_PPR = "PPR " "TWY/TWE.TD.usage.priorPermission(7.1)" ["TWY/TWE.TD.usage.annotation(7.2)"]. |
Reference | Rule |
|---|---|
(7.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}} |
(7.2) | Decode here the annotation with propertyName="priorPermission" and purpose="REMARK", according to the decoding rules for annotations. |
...
(9)
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.
note | Annotations of APN.TD.ApronAreaAvailability shall be translated into free text according to the decoding rules for annotations. |
Items F & G
Leave empty.
Event Update
The eventual update of this type of event shall be encoded following the general rules for
...
...
...
, 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" ["(4)" ("," | "and")] {"APN.BL.name" ["(4)" ("," | "and")]} ("resumed normal operations." |
...
| " : New NOTAM to follow.( |
...
8)" |
...
). |
The following pattern should be used for automatically generating the E field text from the AIXM data
Reference | Rule |
( |
...
8) | 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”. |