...
| Identifier | Data Encoding Rule | Justification | Data Verification Rule (UID) | Remarks | |||||
|---|---|---|---|---|---|---|---|---|---|
| RSG-101 | |||||||||
| If VAL_DIST_VER_UPPER is specified, then UOM_DIST_VER_UPPER and CODE_DIST_VER_UPPER are mandatory. | |||||||||
| If the unit of measurement has the value 'FL' or 'SM', then the attribute CODE_DIST_VER_UPPER must have the value 'STD' (standard pressure). | |||||||||
| If VAL_DIST_VER_LOWER is specified, then UOM_DIST_VER_LOWER and CODE_DIST_VER_LOWER are mandatory. | |||||||||
| When translated to use the same unit of measurement and the same vertical reference, VAL_DIST_VER_LOWER must be lower than or equal to VAL_DIST_VER_UPPER. | |||||||||
| If the unit of measurement has the value 'FL' or 'SM', then the attribute CODE_DIST_VER_LOWER must have the value 'STD' (standard pressure). | |||||||||
| RSG-201 | 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-102202 | The angle between two consecutive segments of the same route cannot exceed 90 degrees.
| EAD Rule | TBD | ||||||
| RSG-103203 | 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-104204 | 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-205 | 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-206 | Route segments of the same Route should be consecutive (no multiple branches): no significant point should appears 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-207 | 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-208 | widthLeft and widthRight must have a value between 0.5 NM and 10 NM. | EAD Rule | TBD |
| |||||
| RSG-209 | 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-210 | The difference between length and the calculated length of the related RouteSegment cannot exceed 5 KM.
| EAD Rule | TBD |
| |||||
| RSG-211 | 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 |
Coding Examples
The figure below gives a simple example of the encoding of the route segment from "DINKI" to "LNO".
...