Text NOTAM production rules
...
Note that if an ad-hoc ATS area is located in the vicinity of one or more airports or affects more than one FIR, there are special provision in the OPADD (Ed. 4.0, section 2.3.9.2) with regard to the NOTAM that need to be issued in order to ensure that the NOTAM appear correctly in the relevant en-route and airport Pre-Flight Information Bulletins (PIB). From a Digital NOTAM point of view, this requires that an Event can have several NOTAM associated, which is supported by the AIXM Event schema. The Event has an explicit associationEvent association to AirportHeliport as defined in ER-09.
...
Reference | Rule | ||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
(1) | If ASE.BL.type does not have the value "CLASS", then use this branch. Otherwise use the other branch, which inserts just the airspace classification. The area type shall be included according to the following decoding table:
| ||||||||||||||||||||||||||||||||||
(2) | If specified, insert here the ASE.BL.name | ||||||||||||||||||||||||||||||||||
| (3) | If specified, insert here the ASE.BL.designator | ||||||||||||||||||||||||||||||||||
| (4) | 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. | ||||||||||||||||||||||||||||||||||
| (5) | If specified, insert here only the ASE.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. | ||||||||||||||||||||||||||||||||||
(6) | Decode the ASE.BL.geometryComponent.lowerLimit/upperLimit (that is part of a ASE.BL.geometryComponent with operation="BASE" or not specified), including reference and unit of measurement, according to the decoding rules for vertical limits | ||||||||||||||||||||||||||||||||||
(7) | 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. | ||||||||||||||||||||||||||||||||||
(8) | If at least one ASE.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 ASE.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) | ||||||||||||||||||||||||||||||||||
(9) | Annotations shall be translated into free text according to the decoding rules for annotations. |
Shall ...