...
The following mapping shall be used for the Q code:
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 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 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.
...
The following pattern should be used for automatically generating the E field text from the AIXM data:
| Code Block | ||||
|---|---|---|---|---|
| ||||
template = ["RSG.BL.RouteAvailability.status(1)"] "route segments open:" \n
"(2)" "/n" "RSG.BL.routeFormed(3)" ("RSG.BL.start.pointChoice(4)"|"RSG.BL.end.pointChoice(4)") " - " ("RSG.BL.start.pointChoice(5)"|"RSG.BL.end.pointChoice(5)") {"Levels(6)"}
{"(2)" "/n" "RSG.BL.routeFormed(3)" ("RSG.BL.start.pointChoice(4)"|"RSG.BL.end.pointChoice(4)") " - " ("RSG.BL.start.pointChoice(5)"|"RSG.BL.end.pointChoice(5)") {"Levels(6)"}} \n
{"." "/n" "RSG.TD.RouteAvailability.annotation(7)"} ".". |
Reference | Rule | |||||||
|---|---|---|---|---|---|---|---|---|
(1) | If for each and everyone of the TD.RouteSegment that are concerned by the Event, during the times (considering an eventual schedule) and at the vertical levels covered by TD having TD.RouteAvailability=CLSD the BL.RouteAvailability.status=COND and BL.RouteAvailability(extension).eASM:conditionalRouteType=CDR1, then insert the text "CDR1". Otherwise insert the text "ATS" | |||||||
(2) | 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) | Insert here the concatenated values of the designatorPrefix, designatorSecondLetter, designatorNumber, multipleIdentifier of the Route portion identified above. | |||||||
(4) | 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) | 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) | If any TD.RouteAvailability/AirspaceLayer has either lowerLevel different from "FLOOR" or upperLevel different from "CEILING" (the segment is not completely closed on the vertical), then insert here each pair lowerLevel - upperLevel of one TD.RouteAvailability.AirspaceLayer having status="CLSD" that exists identically on all TD.RouteAvailability with status "CLSD" of the RouteSegments of the affected route portion, decoded as indicated below:
If the value "FLOOR" is used as TD.RouteAvailability/AirspaceLayer.lowerLimit, then use the BL.lowerLimit, BL.lowerLimit@uom and BL.lowerLimitReference instead. If the value "CEILING" is used as TD.RouteAvailability/AirspaceLayer.upperLimit, then use the BL.upperLimit, BL.upperLimit@uom and BL.upperLimitReference instead. In all situations the values shall be formatted according to the decoding ruled for vertical limits. | |||||||
(7) | Annotations shall be translated into free text according to the common rules for annotations decoding. |
...
The following pattern should be used for automatically generating the E field text from the AIXM data:
| Code Block | ||||
|---|---|---|---|---|
| ||||
template_cancel = "RSG.BL.RouteAvailability.status(1)" "route opening cancels." \n
["New NOTAM to follow.(8)"]. |
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 specify "NEW NOTAM TO FOLLOW" and this text shall be appended at the end of item E of the NOTAM C. Note: in this case, the 4th and 5th letters of the Q code shall also be changed into “XX”. |