...
| Identifier | Data Encoding Rule | Justification | Data Verification Rule (UID) | Remarks |
|---|---|---|---|---|
| RSG-301 | Each Route.Segement shall have as minimum one and as maximum two related RouteAvailability.direction. | Minimum AIP data setTBD | AIXM-5.1_RULE-1A339D (does not include the maximum constraint) | |
| RSG-302 | The value of the RouteAvailability.direction of the same Route.Segement may not have the same value. | Data consistency | TBD | |
| RSG-303 | For each RouteAvailability one and only one discreteLevelSeries shall be provided. | Minimum AIP data set | TBD | The StandardLevelColumn defines if the route segment is flown odd or even. |
| RSG-304 | For RouteAvailability.direction the values 'BOTH' and 'OTHER' shall not be used. | Data consistency | TBD | In case a of a bidirectional route, two records shall be encoded - one for forward and one for backward. |
...
More coding examples can be found in the DONLON AIP data set file:
| No. | Description | XPath Expression |
|---|---|---|
| RSG-EX-01 | Route segment of Lower ATS route with forward & backward with FL series Even & Odd respectively. | //aixm:RouteSegmentTimeSlice[@gml:id='RSG_A6_BOR_ROB'] | |
| RSG-EX-02 | Route segment of Upper ATS route with forward & backward with FL series Even & Odd respectively. | //aixm:RouteSegmentTimeSlice[@gml:id='RSG_UA4_BARIM_WOB'] |
| RSG-EX-03 | Route segment RNAV Route with direction forward & backward with FL series Even & Odd respectively. | //aixm:RouteSegmentTimeSlice[@gml:id ='RSG_UL123_ABOLA_ILURU'] |