...
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 RSG.BL. indicates that the corresponding data item must be taken from the RouteSegment BASELINE which is valid at the start time of the Event;
- the abbreviation RSG.TD. indicates that the corresponding data item must be taken from the RouteSegment TEMPDELTA that was created for the Event;
- Note: According to encoding rule ER-08, the TEMPDELTA might also include RouteAvailability elements that have been copied from the BASELINE data for compliance with the AIXM Temporality rules. For RTE.OPN scenario such static information shall be included in the text NOTAM generation algorithm to assure clarity with respect to the route status.
...
Identify the FIR(s) within which the RouteSegments concerned by the Event are located.
...
RSG.BL.navigationType | Corresponding Q codes |
|---|---|
RNAV or TACAN (for all RouteSegments concerned by the Event) | QANLC |
otherwise | QARLC |
...
- the lowest value between all RSG.TD.RouteAvailability/AirspaceLayer.lowerLimit associated with the Event, formatted according to the common rules for {{Lower limit / Upper limit}}, shall be used as Lower limit;
- the highest value between all RSG.TD.RouteAvailability/AirspaceLayer.upperLimit upperLimit associated with the Event, formatted according to the common rules for {{Lower limit / Upper limit}}, shall be used as Upper limit.
...
Items B and C shall be decoded following the common production rules.
If at least one RSG.TD.RouteAvailability.timeInterval exists (the Event has an associated schedule), then select the RSG.TD.RouteAvailability.timeInterval(s) that have RSG.TD.RouteAvailability.status='CLSD' and and represent them in item D according to the common NOTAM production rules for {{Item D, E - Schedules}}. Otherwise, item D shall be left empty.
...
- only the closure schedules will be translated in the NOTAM Text. Eventual opening times described as schedules are considered as having been copied from the BASELINE, for completeness sake (see ER-06);
- according to the input template, a single set of schedules is applicable to all RouteSegment closures associated with the Event. This will be ensured with a data verification rule. Therefore, it is sufficient to decode the schedules associated with one of the RSG.TD.RouteAvailability.timeInterval.
Item E
The following pattern should be used for automatically generating the E field text from the AIXM data:
...
Reference | Coding keywords | Rule | |||||||
|---|---|---|---|---|---|---|---|---|---|
(1) | route availability | If for each and everyone of the RSG.TD.RouteSegment that are concerned by the Event, during the times (considering an eventual schedule) and at the vertical levels covered by TD having RSG.TD.RouteAvailability='CLSD' the RSG.BL.RouteAvailability.status='COND' and RSGRSG.BL.RouteAvailability(extension).ADR:conditionalRouteType='CDR1', then insert the text "CDR1". Otherwise insert the text "ATS" | |||||||
(2) | route designator, start point, end point | Identify the route portions concerned and repeat steps from 3 to 5 for each route portion. To identify the route portions, order the RouteSegments associated with the Event:
| |||||||
(3) | route designator | Insert here the concatenated values of the designatorPrefix, designatorSecondLetter, designatorNumber, multipleIdentifier of the Route portion identified above. | |||||||
(4) | start point | Insert here the DesignatedPoint.designator or the Navaid.designator or the AirportHeliport.designator that was identified as start of a route portion at point (2) above. Note that this could be either the start or the end of a RouteSegment, as it is not guaranteed that the RouteSegments have been encoded in a regular P1-P2/P2-P3/P3-P4/... order. There could be situations where the segments have been encoded as P1-P2/P3-P2/P3-P4/etc. | |||||||
(5) | end point | Insert here the DesignatedPoint.designator or the Navaid.designator or the AirportHeliport.designator that was identified as end of a route portion at point (2) above. Note that this could be either the start or the end of a RouteSegment, as it is not guaranteed that the RouteSegments have been encoded in a regular P1-P2/P2-P3/P3-P4/... order. There could be situations where the segments have been encoded as P1-P2/P3-P2/P3-P4/etc. | |||||||
(6) | lower limit, upper limit | If any RSG.TD.RouteAvailability/AirspaceLayer AirspaceLayer has either lowerLevel different from "'FLOOR" or ' or upperLevel different from "'CEILING" ' (the segment is not completely closed on the vertical), then insert here each pair lowerLevel - upperLevel of one RSG.TD.RouteAvailability.AirspaceLayer AirspaceLayer having status="'CLSD" ' that exists identically on all RSG.TD.RouteAvailability with status "'CLSD" ' of the RouteSegments of the affected route portion, decoded as indicated below:
| |||||||
| (7) | direction | Insert here the RouteAvailability.direction direction as follows:
If both directions are to be included for the levels selected, insert here "forward and backward". | |||||||
| (8) | Follow this branch if there are RouteAvailability objects with a Note having purpose='REMARK' and the text="Baseline data copy." for the duration of the event. Otherwise ignore this branch. | ||||||||
| (9) | Insert here the AirspaceLayers of the RouteAvailability objects with a Note having purpose='REMARK' and the text="Baseline data copy." decoded as in rule (6) above regardless of the status. If the Event has an associated schedule, consider only the AirspaceLayers timeSheets /Timesheets corresponding to the closure schedule. | ||||||||
| (10) | Insert here the RouteAvailability.status for each of the levels and directions corresponding to the AirspaceLayers selected on (9). | ||||||||
(11) | note | Annotations shall be translated into free text according to the common rules for annotations decoding. |
...