| Warning | ||
|---|---|---|
| ||
Open comments are available at: https://docs.google.com/document/d/1T0g56igUsV5anCb4roIAcq9zSA1DlM-BJTHj-w0Rho8/ Scenario is work in progress. |
Text NOTAM production rules
...
The following mapping shall be used for the Q code:
BL.navigationType | Corresponding Q codes |
RNAV or TACAN (for all RouteSegments concerned by the Event) | QANLC |
otherwise | QARLC |
Scope
Insert the value ‘E’.
...
The following pattern should be used for automatically generating the E field text from the AIXM data:
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. |
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).
...
If a NOTAM C is produced, then the 4th and 5th letters (the "condition") of the Q code shall be "CN", except for the situation of a “new NOTAM to follow, in which case “XX”shall be used. and t
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 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”. |