...
Tracks and reverse tracks if any, have to be encoded taking into account the implicit direction of the route segment, i.e. the defined start and end point, (see also above). In this regard the tracks are considered to be from the start point of the segment whereas the reverse tracks are considred to be to from the end point of the route segment.
| Info | ||
|---|---|---|
| ||
AIXM 5.1.1 does not provdie the possibility to define if the path between on the route segment is a VOR radial. Shall 'OTHER:VOR_RADIAL' for RouteSegment.pathType be used for that purpose. |
...
ENR 3.4 (Helicopter Routes):
upper and lower limits; minimum flight altitudes
ENR 3.5 (Other Routes):
No requirements stated regarding vertical limits.
The following table gives an overview which vertical limits are required by PANS-AIM for the AIP data set and the corresponding AIXM attributes of the RouteSegment class (Note 1) :
| PANS-AIM | AIXM 5.1.1 | Remarks | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Property | Definition/Desription | Relevance | Attribute | DescriptionRemarks | ||||||
| Upper limit | The upper limit of the route segment | ENR 3.1-3.4 | upperLimit | The vertical position of the route segment ceiling. | ||||||
| Lower Limit | The lower limit of the route segment | ENR 3.1-3.4 (Note 2) | lowerLimit | The vertical position of the route segment floor. |
| |||||
| Minimum obstacle clearance altitude (MOCA) | The minimum altitude for a defined segment of flight that provides the required obstacle clearance. minimumObstacleClearingAltitude | ENR 3.1 Lower ATS Route | minimumObstacleClearanceAltitude | Minimum obstacle clearance altitude (MOCA). The minimum altitude for a defined segment of flight that provides the required obstacle clearance. | According to PANS-OPS
In PANS-AIM it is only required for ENR 3.1Lower ATS Routes. The MOC value to be applied in the primary area for the en-route phase of an IFR flight is 300 m (1 000 ft) as a minimum. | |||||
| Minimum en-route altitude (MEA) | The altitude for an en-route segment that provides adequate reception of relevant navigation facilities and ATS communications, complies with the airspace structure and provides the required obstacle clearance. | ENR 3.1 Lower ATS Route (Note 2) | minimumEnrouteAltitude | Minimum en-route altitude (MEA). The altitude for an en-route segment that provides adequate reception of relevant navigation facilities and ATS communications, complies with the airspace structure and provides the required obstacle clearance. | According to PANS-OPS
| |||||
| Minimum flight altitude | Minimum flight altitude | ENR 3.4 Helicopter routes | ??? | According to PANS-AIM
In PANS-AIM the term is only used for "ENR 3.4 Helicopter routes" ICAO ANnex 11, 2.22 Minimum flight altitudes
| ||||||
| NA | NA | NA | minimumCrossingAtEnd | The lowermost vertical position at the end point, when flying on the route portion in the direction indicated in the RoutePortionUsage. |
| |||||
| NA | NA | NA | maximumCrossingAtEnd | The uppermost vertical position at the end point, when flying on the route portion in the direction indicated in the RoutePortionUsage. | Same issue as above. | |||||
| Note | ||
|---|---|---|
| ||
| PANS-AIM defines more vertical limits, i.e Area Minimum Altitude (AMA) and Minimum Vectoring Altitude (MVA) which are not considered as part of the AIP Data set and hence are not conatined in the table. |
| Info | ||
|---|---|---|
| ||
In some State AIPs, an additional limit, "overriding" the Lower limit specification is published. To publish this minimum limit, often statements such as " but at least" are used. The Lower limit override always refers to ground e.g. "feet above ground". How to encode this in AIXM 5.1.1? in AIXM 4.5 a dedicated attribute was provided VAL_DIST_VER_LOWER_OVRDE Example:
|
...
| Identifier | Data Encoding Rule | Justification | Data Verification Rule (UID) | Remarks |
|---|---|---|---|---|
| RSG-201 | ASE-202 | ASE-203 | ASE-204 |
Coding Examples
...
| 101 | Two consecutive route segments (of the same Route) should have vertical limits that, if not overlapping, should not be further away than 1000 FT. For example, if segment 1 is FL245 to FL295 and segment 2 is FL310 to FL490, (this rule will need to be adjusted based on operational experience).
| EAD Rule | TBD | ||||||
| RSG-102 | The angle between two consecutive segments of the same route cannot exceed 90 degrees.
| EAD Rule | TBD | ||||||
| RSG-103 | At the border (defined as a buffer area of 2 km on each side) between two areas of responsibility, route segments should be continued by route segments of the same or another Route. | EAD Rule |
| ||||||
| RSG-104 | Route segments of the same Route should be consecutive (no gaps): not more than two significant points should be either the start or the end of a single route segment. | EAD Rule | |||||||
| Route segments of the same Route should be consecutive: no segment should be described in the opposite order of significant points (start instead of end and vice-versa) compared to the adjacent segments. | |||||||||
Coding Examples
The figure below gives a simple example of the encoding of the route segment from "DINKI" to "LNO".
The figures below gives an example of the encdoing of the route segment (from "BARIM" to "WOB") including the mapping from AIXM UML to AIXM XML.
More examples TBD in the scope of the DONLON AIP data set XML.