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:
APE.BL.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 APE.BL.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:
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) | apron name | 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) | location and extent description | Insert here the APE.BL.annotation note with propertyName="extent" and purpose='DESCRIPTION' translated into free text according to the decoding rules for annotations. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
(6) | conditional for closed, except for prohibited for additionally allowed for | Insert here APE.BL.availability.ApronAreaAvailability.usage.ApronAreaUsage.type 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.
*Note: value is unlikely to be used in a NOTAM, its decoding is provided for completeness sake.
**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:
*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:
*Note: value is unlikely to be used in a NOTAM, its decoding is provided for completeness sake. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
(9) | If there exists a parent APE.BL.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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
(10) | PPR time PPR details | If APE.BL.usage.priorPermission is not NIL, then insert here the decoding of the PPR information as detailed in the following diagram:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
(11) | reason | If there exists a APE.BL.availability.annotation having propertyName='operationalStatus' and purpose='REMARK', then translate it into free text according to the decoding rules for annotations. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
(12) | note | Annotations of APE.BL.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
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”. |