Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: SBVR applied, minor editorial

Definition

...

Data item

value

AIXM mapping

route availability

An explicit indication that the route portion is closed.

RouteSegment/RouteAvailability.status with the list of values CodeRouteAvailabilityType

route designator

The published designator of the route concerned. This information, in combination with the start/end point is used to identify the route segments concerned.

RouteSegment.routeFormed

start point

The designator and eventually the type (in the case of a Navaid) of the significant point from where the route availability is affected. This information, in combination with the route designator and the end point is used to identify the route segments concerned.

RouteSegment.start/EnRouteSegmentPoint.pointChoice

end point

The designator and eventually the type (in the case of a Navaid) of the significant point until where the route availability is affected. This information, in combination with the route designator and the start point is used to identify the route segments concerned.

RouteSegment.end/EnRouteSegmentPoint.pointChoice

lower limit

The vertical level above which and including that level is affected by the closure.

RouteSegment/RouteAvailability/AirspaceLayer.lowerLimit and lowerLimitReference

upper limit

The vertical level below which and including that level is affected by the closure.

RouteSegment/RouteAvailability/AirspaceLayer.upperLimit upperLimit and upperLimitReference

direction An indication of the direction in which the route segment is considered for closure. RouteSegment/RouteAvailability.direction

start time

The effective date & time when the closure starts. This might be further detailed in a "schedule".e

RouteSegment/RouteSegmentTimeSlice/TimePeriod.beginPosition, Event/EventTimeSlice.validTime/timePosition and Event/EventTimeSlice.featureLifetime/beginPosition

end time

The effective date & time when the closure ends.

RouteSegment/RouteSegmentTimeSlice/TimePeriod.endPosition and Event/EventTimeSlice.featureLifetime/endPosition also applying the rules for {{Events with estimated end time}}

schedule

A schedule might be provided in case of the closure is only being effective according to a regular timetable, within the period between the start time and the end time.

RouteSegment/RouteAvailability/Timesheet/… according to the rules for {{Schedules}}

note

A free text note that provides further details concerning the route closure, such as reason, alternate routes, etc.

Route/RouteAvailability.annotation with purpose=”REMARK”REMARK

Notes:

  • It is recommended that data input applications allow the operator to visualise graphically the route segments that are closed, in the context of the overall airspace structure.

...

  • It is assumed that information about the route segments concerned already exists in the form of RouteSegment of RouteSegment BASELINE TimeSlice(s) covering the complete period of validity of the event, coded as specified in the Coding Guidelines for the (ICAO) AIP Data Set - Route [RTE].
    (Proposal for encoding rule - It is assumed that RouteAvailability information exists in the BASELINE data covering as a minimum the direction, status and associated AirspaceLayers. Furthermore, it is assumed that a clear indication of the status exists for' FORWARD' and BACKWARDS 'BACKWARD' direction. The absence of one would make unclear its status)
  • It is assumed that all RouteSegment affected by the closure have a similar availability/RouteAvailability.status, e.g. 'OPEN', 'COND'.

Data encoding rules

The data encoding rules provided in this section shall be followed in order to ensure the harmonisation of the digital encodings provided by different sources. The compliance with some of these encoding rules can be checked with automatic data validation rules.

Identifier

Data encoding rule

ER-01

The temporary closure of a route portion shall be encoded as:

  • a new Event with a BASELINE TimeSlice (encoding=”DIGITAL”, scenario=”RTE.CLS”, version=”2.0”), for which a PERMDELTA TimeSlice may also be provided; and
  • a new TEMPDELTA Timeslice TimeSlice for each individual RouteSegment that is located on the route portion specified in the event data. It is recommended that data provider interfaces allow the encoding of the route portion closure at once and that the application takes care of converting the information into Timeslices TimeSlices for the individual RouteSegment(s) concerned.

ER-02

The "route designator" shall be used in order to identify the route concerned, in order to instantiate the value of the RouteSegment.routeFormed property. If multiple routes exist with that designator, then the "start point" and "end point" information shall also be considered in order to identify the route concerned.

ER-03

A RouteAvailability object with status='CLSD'direction and at least one associated level.AirspaceLayer object shall be included in the TEMPDELTA Timeslice TimeSlice for each RouteSegment concerned.

ER-04

If no lower limit is specified in the Event data input, then the associated level.AirspaceLayer should contain the values lowerLimit="'FLOOR" (uom='OTHER"').

ER-05

If no upper limit is specified in the Event data input, then the associated level.AirspaceLayer should contain the values lowerLimit="CEILING" ' (uom='OTHER"').

ER-06A maximum of two directions ('FORWARD' and BACKWARDS'BACKWARD') can be provided for each pair of upper and lower limit. 

ER-07

Note that in accordance with the AIXM Temporality Concept, the RouteAvailability associated with the TEMPDELTA completely replaces all the BASELINE RouteAvailability information, during the TEMPDELTA time of applicability. Therefore, if the temporary closure only concerns certain times, direction and/or levels, the other times, direction and/or levels, when the route eventually remains open/conditional, shall be explicitly included in the TEMPDELTA. The calculation of the necessary additional RouteAvailability elements to be included in the TEMPDELTA shall be automatically done by the applications implementing this specification.

All RouteAvailability All RouteAvailability elements that are copied from the BASELINE data for completeness sake shall get an associated Note with purpose='REMARK' and the text="Baseline data copy." It is recommended that the input interface provides a "calendar/level" view of the route portion availability, enabling the operator to graphically check the status of the route availability at different times and levels, such as in the example below:

In the calendar view, the Baseline information that remains valid during the Event validity time shall be visibly identified from the information that is specific to the Event, for example by using a different colour fill pattern.

...