| Panel | ||
|---|---|---|
| ||
|
...
For Route Segment, PANS-AIM requires some basic properties as part of the minimum AIP data set. This is
...,from point, to point, track, distance, upper limit, lower limit, MEA, MOCA, ...
...
The actual start or end point of a RouteSegment is defined via the pointChoice property that allows to select a SignificantPoint. Not all available choices of significant points (e.g. RunwayCentrelinePoint, etc.) will make sense to be used for a route segment point (see also page SignificantPoint [SPN] ).
Mainly DesignatedPoint and Navaid will be the start or end point of a RouteSegment. In a few countries, also the airport reference point of an AirportHeliport may be used for that purpose.
For defining that the point used for the route segment is an RNAV waypoint (see also topic Designated Point (Overview)) the EnrouteSegmentPoint.waypoint attribute will be encoded with 'YES'.
In addition, AIXM 5 provides as an option to encode the extend of the route segment as geometrical element, using the Curve class. This data may be used for charting purposes. The curve will be encoded according to the corresponding GML specification (see topic Geometry (Overview)). It will contain the coordinates of the start and end point of the route segment. It shall be ensured that the data (i.e. coordinates) provided in the Curve element(s) match with those provided as start and end of the RouteSegment.
...
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.
| Infonote | ||
|---|---|---|
| ||
AIXM 5.1.1 does not provide the possibility a dedicated value to define if the path between on the route segment is a VOR radial. Shall 'OTHER:VOR_RADIAL' may be used for RouteSegment.pathType be used for that purpose?. |
The length attribute allows to define the 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').
...
| Warning | ||
|---|---|---|
| ||
PANS-AIM defines an accuracy for the values for the length of an Route Segment. There is no dedicated attribute in AIXM 5.1.1. Workaround fro AIXM 5.1(.1): A Note may be used to encode that information. Status AIXM 5.2: See CCB AIXM-269. |
Lateral Limits
...
| 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:
|
Regarding the general encoding guidelines and rules for vertical limits see topic Vertical Limits.
...
| Identifier | Data Encoding Rule | Justification | Data Verification Rule (UID) | Remarks | |||
|---|---|---|---|---|---|---|---|
| RSG-101 | RouteSegment.navigationType is mandatory. | Minimum AIP data set | AIXM-5.1_RULE-1A3351 | ||||
| RSG-102 | RouteSegment.start is mandatory. | Minimum AIP data set | AIXM-5.1_RULE-1B09E2 | ||||
| RSG-103 | RouteSegment.end is mandatory. | Minimum AIP data set | AIXM-5.1_RULE-1B09E1 | ||||
| RSG-104 | RouteSegment.start.EnRouteSegmentPoint.reportingATC is mandatory. | Minimum AIP data set | TBD | ||||
| RSG-105 | RouteSegment.end.EnRouteSegmentPoint.reportingATC is mandatory. | Minimum AIP data set | TBD | ||||
| RSG-106 | Either RouteSegment.trueTrack or RouteSegment.magneticTrack shall be provided where RouteSegment.availability.RouteAvailability.direction value equal-to ‘'FORWARD''. | Minimum AIP data set | TBD | ||||
| RSG-107 | Either RouteSegment.reverseTrueTrack or RouteSegment.reverseMagneticTrack shall be provided where RouteSegment.availability.RouteAvailability.direction value equal-to ‘'BACKWARD''. | Minimum AIP data set | TBD | ||||
| RSG-108 | RouteSegment.length is mandatory. | Minimum AIP data set | TBD | ||||
| RSG-109 | RouteSegment.pathType is mandatory. | Minimum AIP data set | TBD | ||||
| RSG-110 | The RouteSegment.pathType should 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' | Minimum AIP data set | TBD | ||||
| RSG-112 | RouteSegment.upperLimit is mandatory. | Minimum AIP data set | TBD | ||||
| RSG-113 | RouteSegment.upperLimitReference is mandatory. | Data consistency | TBD | ||||
| RSG-114 | Either RouteSegment.lowerLimit or RouteSegment.minimumEnrouteAltitude shall be provided. | Minimum AIP data set | TBD | ||||
| RSG-115 | If RouteSegment.lowerLimit is specified, then RouteSegment.lowerLimitReference is mandatory. | AIXM Model / Minimal data rule | AIXM-5.1_RULE-1A13DB | ||||
| RSG-116 | For ENR 3.1 Lower ATS routes RouteSegment.level shall be equal-to 'LOWER' | Data completeness | N/A | Needed for other data verification rules | |||
| RSG-117 | For ENR 3.2 Upper ATS routes RouteSegment.level shall be equal-to 'UPPER' | Data completeness | N/A | Needed for other data verification rules | |||
| RSG-118 | If RouteSegment.level is equal-to 'LOWER' than, RouteSegment.minimumObstacleClearanceAltitude is mandatory. | Minimum AIP data set | TBD | MOCA is mandatory for ENR 3.1 Lower ATS Routes | |||
| RSG-119 | If RouteSegment.level is equal-to 'LOWER' or 'UPPER' than, RouteSegment.widthLeft and RouteSegment.widthRight is mandatory for | PANS-AIM ENR 3.1 & ENR 3.2 | TBD | Width is mandatory for ENR 3.1 Lower ATS Routes and ENR 3.2 Upper ATS Routes. | |||
| RSG-120 | RouteSegment.widthLeft and RouteSegment.widthRight shall have the same uom. | Data consistency | AIXM-5.1_RULE-D4A71 | ||||
| RSG-121 | RouteSegment.requiredNavigationPerformance is mandatory. | Minimum AIP data set | TBD | ||||
| RSG-122 | If RouteSegment.minimumCrossingAtEnd is specified, then RouteSegment.minimumCrossingAtEndReference is mandatory. | AIXM Model / Minimal data rule | AIXM-5.1_RULE-1A13DC | ||||
| RSG-123 | If RouteSegment.minimumCrossingAtEnd is specified, then RouteSegment.minimumCrossingAtEndReference is mandatory. | AIXM Model / Minimal data rule | AIXM-5.1_RULE-1A13DC | ||||
| RSG-124 | RouteSegment.lowerLimit shall not be equal-to 'FLOOR' or 'CELLING' or 'UNL'. | EAD / Data consistency | AIXM-5.1_RULE-F07AB (Rule does not take into account UNL) | ||||
| RSG-125 | RouteSegment.upperLimit shall not be equal-to 'FLOOR' or 'CELLING' or 'GND'. | EAD / Data consistency | AIXM-5.1_RULE-F07AC (Rule does not take into account GND) | ||||
| RSG-126 | RouteSegment.minimumObstacleClearanceAltitude shall not be equal-to 'FLOOR' or 'CELLING' or 'UNL'. | EAD / Data consistency | AIXM-5.1_RULE-F07A9 (Rule does not take into account UNL) | ||||
| RSG-127 | RouteSegment.minimumEnrouteAltitude shall not be equal-to 'FLOOR' or 'CELLING' or 'UNL'. | EAD / Data consistency | AIXM-5.1_RULE-F07AA (Rule does not take into account UNL) | ||||
| RSG-128 | The value 'OTHER' shall not be used for RouteSegment.level. | AIXM4.5 / Standard | AIXM-5.1_RULE-C2D31 | ||||
| RSG-129 | The value 'OTHER' shall not be used for RouteSegment.lowerLimit.uom | AIXM4.5 / Standard | AIXM-5.1_RULE-C2D38 | ||||
| RSG-130 | The value 'OTHER' shall not be used for RouteSegment.upperLimit.uom | AIXM4.5 / Standard | AIXM-5.1_RULE-C2D39 | ||||
| RSG-131 | The value 'OTHER' shall not be used for RouteSegment.widthLeft.uom | AIXM4.5 / Standard | AIXM-5.1_RULE-C2D3D | ||||
| RSG-132 | The value 'OTHER' shall not be used for RouteSegment.widthRight.uom | AIXM4.5 / Standard | AIXM-5.1_RULE-C2D3E | ||||
| RSG-133 | The value 'OTHER' shall not be used for RouteSegment.length.uom | AIXM4.5 / Standard | AIXM-5.1_RULE-C2D3F | ||||
| RSG-134 | Each RouteSegment shall have assigned routeFormed value. | AIXM Model / Minimal data rule | AIXM-5.1_RULE-1A33EF | ||||
| RSG-135 | If the RouteSegment.lowerLimit.uom has the value 'FL' or 'SM', then the attribute RouteSegment.lowerLimitReference must have the value 'STD'. | AIXM 4.5 Business Rules / Data consistency | AIXM-5.1_RULE-1A4E62 | ||||
| RSG-136 | If the RouteSegment.upperLimit.uom has the value 'FL' or 'SM', then the attribute AirspaceVolume.upperLimitReference must have the value 'STD'. | AIXM 4.5 Business Rules / Data consistency | AIXM-5.1_RULE-1A4E68 | ||||
| RSG-137 | If the RouteSegment.minimumCrossingAtEnd.uom has the value 'FL' or 'SM', then the attribute RouteSegment.minimumCrossingAtEndReference must have the value 'STD'. | AIXM 4.5 Business Rules / Data consistency | AIXM-5.1_RULE-1A4E6B | ||||
| RSG-138 | If the RouteSegment.maximumCrossingAtEnd.uom has the value 'FL' or 'SM', then the attribute RouteSegment.maximumCrossingAtEndReference must have the value 'STD'. | AIXM 4.5 Business Rules / Data consistency | AIXM-5.1_RULE-1A4E6F | ||||
| RSG-139 | When translated to use the same unit of measurement and the same vertical reference, RouteSegment.lowerLimit must be lower than or equal to RouteSegment.upperLimit. | Data consistency | TBD | ||||
| RSG-140 | 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-141 | The accuracy value of the RouteSegment.length shall be 0.1 km or less. | PANS-AIM | N/A | Can only be coded as annotation for the length attribute. | |||
| RSG-142 | The value of the RouteSegment.length shall be published with at least 1 decimals of KM or NM resolution. | PANS-AIM | TBD | ||||
| RSG-143 | The accuracy value of the RouteSegment.minimumEnrouteAltitude shall be 50 m or less. | PANS-AIM | N/A | Can only be coded as annotation for the length attribute. | |||
| RSG-144 | The accuracy value of the RouteSegment.minimumObstacleClearanceAltitude shall be 50 m or less. | PANS-AIM | N/A | Can only be coded as annotation for the length attribute. | |||
| RSG-145 | The value of the RouteSegment.minimumEnrouteAltitude shall be published with at least 50 m or 100 ft resolution. | PANS-AIM | N/A | ||||
| RSG-146 | The value of the RouteSegment.minimumObstacleClearanceAltitude shall be published with at least 50 m or 100 ft resolution. | PANS-AIM | N/A | ||||
| RSG-901 | 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-902 | The angle between two consecutive segments of the same route cannot exceed 90 degrees.
| EAD Rule | TBD | ||||
| RSG-903 | 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 | ||||
| Info | title | Open Question RSG_1-4This rule is based on the areas of responsibility defined in EAD. Shall there be a similar rules for the AIP data set based e.g.on FIR/UIR? | |||||
| RSG-904 | 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-905 | 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-906 | 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-907 | 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-908 | widthLeft and widthRight must have a value between 0.5 NM and 10 NM. | EAD Rule | TBD | ||||
| RSG-909 | 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-910 | The difference between length and the calculated length of the related RouteSegment cannot exceed 5 KM.
| EAD Rule | TBD| Info | | | Open Question RSG 1-6 | PANS-AIM requires an accuracy of 1/10 KM. Shall the rule be changed accordingly? | |
| RSG-911 | 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 |
...
More coding examples can be found in the AIXM DONLON AIP data set AIP Data Set - Specimen (DONLON).
| No. | Description | XPath Expression |
|---|---|---|
RSG-EX-01 RSG-EX-04 | Route segment of Lower ATS route (incl. MEA) Route segment of Lower ATS route (incl. MOCA) | //aixm:RouteSegmentTimeSlice[@gml:id='RSG_A6_BOR_ROB'] | //aixm:RouteSegmentTimeSlice[@gml:id='RSG_A6_ROB_ROK'] |
| RSG-EX-02 | Route segment of Upper ATS route | //aixm:RouteSegmentTimeSlice[@gml:id='RSG_UA4_BARIM_WOB'] |
| RSG-EX-03 | Route segment of RNAV route | //aixm:RouteSegmentTimeSlice[@gml:id='RSG_UL123_ABOLA_ILURU'] |
...