For Route Segment, PANS-AIM requires some basic properties as part of the minimum AIP data set. This is the startpoint and endpoint of the route, track, distance, upper limit, lower limit, MEA and MOCA.
The diagram below shows the AIXM classes, including the relevant Data Types, needed to encode that information:
Start Point & End Point
Route Segment ICAO defines a route segment as
...
Tracks and reverse tracks if any, shall 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 from the start point of the segment, whereas the reverse tracks are from the end point of the route segment.
| Info | ||
|---|---|---|
| ||
AIXM 5.1.1 does not provide 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? |
The length attribute allows to define the length distance of the path of the RouteSegment. The length depends on the pathType, which may be a great circle ('GRC'), a rhumbline ('RHL') or a geodesic line ('GDS').
...
| PANS-AIM | AIXM 5.1.1 | Remarks | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Property | Definition/Description | Relevance | Attribute | Description | ||||||
| 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.1 Lower 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 contained 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-101 | RouteSegment.navigationType is mandatory. | PANS-AIMMinimum AIP data set | TBD |
| |||||
| RSG-102 | RouteSegment.start is mandatory. | PANS-AIMMinimum AIP data set | TBD | ||||||
| RSG-103 | RouteSegment.end is mandatory. | PANS-AIMMinimum AIP data set | TBD | ||||||
| RSG-104 | RouteSegment.start.EnRouteSegmentPoint.reportingATC is mandatory. | PANS-AIMMinimum AIP data set | TBD | ||||||
| RSG-105 | RouteSegment.end.EnRouteSegmentPoint.reportingATC is mandatory. | PANS-AIMMinimum AIP data set | TBD | ||||||
| RSG-106 | Either RouteSegment.trueTrack or RouteSegment.magneticTrack shall be provided where RouteSegment.availability.RouteAvailability.direction value equal-to ‘'FORWARD''.PANS-AIM | Minimum AIP data set | TBD | Or shall the track always be specified independent of the route segment availability? Is it possible that a route segment is available just backward | |||||
| RSG-107 | Either RouteSegment.reverseTrueTrack or RouteSegment.reverseMagneticTrack shall be provided where RouteSegment.availability.RouteAvailability.direction value equal-to ‘'BACKWARD''.PANS-AIM | Minimum AIP data set | TBD | ||||||
| RSG-108 | RouteSegment.length is mandatory. | PANS-AIMMinimum AIP data set | TBD | ||||||
| RSG-109 | RouteSegment.pathType is mandatory. | PANS-AIMMinimum AIP data set | TBD | ||||||
| RSG-110 | The RouteSegment.pathType shall have value equal-to 'GDS'. | PANS-AIM ENR 3 | TBD | Only in case path of the route segment is really a geodesic line. | |||||
| RSG-111 | The accuracy of the length of the route segment shall be encoded as RouteSegment.annotation.Note.propertyNamevalue equal-to 'length' PANS-AIM | Minimum AIP data set | TBD | ||||||
| RSG-112 | RouteSegment.upperLimit is mandatory. | PANS-AIMMinimum AIP data set | TBD | ||||||
| RSG-113 | RouteSegment.upperLimitReference is mandatory. | PANS-AIMdata consistency | TBD | ||||||
| RSG-114 | Either RouteSegment.lowerLimit or RouteSegment.minimumEnrouteAltitude shall be provided. | PANS-AIMMinimum AIP data set | TBD | ||||||
| If RouteSegment.lowerLimit is specified, then RouteSegment.lowerLimitReference is mandatory. | PANS-AIMData consistency | TBD | |||||||
| RSG-115 | RouteSegment.minimumObstacleClearanceAltitude is mandatory for ENR 3.1 Lower ATS Routes. | PANS-AIMMinimum AIP data set | TBD |
| |||||
| RSG-116 | RouteSegment.widthLeft and RouteSegment.widthRight is mandatory for ENR 3.1 Lower ATS Routes and ENR 3.2 Upper ATS Routes. | PANS-AIMAIM ENR 3.1 & ENR 3.2 | TBD | ||||||
| RSG-117 | RouteSegment.requiredNavigationPerformance is mandatory. | PANS-AIMMinimum AIP data set | TBD |
See also rule RSG-101 | |||||
| RSG-118 | If the uomDistanceVerticalType has the value ''FL'' or ''SM'', then the attribute upperLimitReference must have the value ''STD'' (standard pressure). | Data consistency | TBD | ||||||
| RSG-119 | When translated to use the same unit of measurement and the same vertical reference, lowerLimit must be lower than or equal to upperLimit. | Data consistency | TBD | ||||||
| RSG-120 | If the uomDistanceVerticalType has the value ''FL'' or ''SM'', then the attribute lowerLimitReference must have the value ''STD'' (standard pressure). | Data consistency | TBD | ||||||
| RSG-121 | The EnRouteSegmentPoint.pointChoice used as RouteSegment.start or RouteSegment.start may not be other than a DesignatedPoint or a Navaid or an AirportHeliport. | Data consistency | TBD | ||||||
| RSG-201901 | 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-202902 | The angle between two consecutive segments of the same route cannot exceed 90 degrees.
| EAD Rule | TBD | ||||||
| RSG-203903 | 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 | TBD |
| |||||
| RSG-204904 | 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 | TBD |
According to the rule definition the rule is violated, because four significant points "KPT", "TGO", "KRH" and "ECCHO" are used only once, either as start or end point of a route segment. | |||||
| RSG-205905 | 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. | EAD Rule | TBD |
In the given example the rule is violated, because route segment "ECCHO - ANEKI" is described in the opposite order of the adjacent segments. | |||||
| RSG-206906 | Route segments of the same Route should be consecutive (no multiple branches): no significant point should appear on 3 or more segments, either as start or as end point. | EAD Rule | TBD |
According to the rule definition the rule is violated, because ANEKI appears on three route segments. Subsequently this results in multiple branches; "ANEKI - ECCHO" and ANEKI - RUDUS". | |||||
| RSG-207907 | The position of the SignificantPoint used as the beginning of the RouteSegment must be separated by at least 30m (1 sec of arc) from the position of the SignificantPoint used as the end of the RouteSegment.
| EAD Rule | TBD | ||||||
| RSG-208908 | widthLeft and widthRight must have a value between 0.5 NM and 10 NM. | EAD Rule | TBD |
| |||||
| RSG-209909 | The value of EnRouteSegmentPoint.reportingATC for RouteSegment.start and RouteSegment.end of any two consecutive segments of the same route must be consistent. | EAD Rule | TBD | In case of FIR BRDY points there are situations when the source data of the concerned neighbouring countries do not match. For example on routes crossing the border between Latvia and Sweden, the report at the border points is specified 'on request' in the Sweden AIP and as 'compulsory' in the Latvia AIP. | |||||
| RSG-210910 | The difference between length and the calculated length of the related RouteSegment cannot exceed 5 KM.
| EAD Rule | TBD |
| |||||
| RSG-211911 | The difference between Initial trueTrack and the calculated initial true track of the related RouteSegment cannot exceed 2 degrees. The difference between reverseTrueTrack and the calculated reverse initial true track of the related RouteSegment cannot exceed 2 degrees.
| EAD Rule | TBD |
...
The figures below give an example of the encoding of the route segment (from "BARIM" to "WOB"), including the mapping from AIXM UML to AIXM XML.
More coding examples TBD can be found in the scope of the AIXM DONLON AIP data set XML..
| No. | Description | XPath Expression |
|---|---|---|
| RSG-1 | Route Segments | //aixm:RouteSegment |