Versions Compared

Version Old Version 10 New Version 11
Changes made by

Andreea Perca

Andreea Perca

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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 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 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=BOTH and at least one associated level.AirspaceLayer object shall be included in the TEMPDELTA Timeslice for each RouteSegment concerned.

A RouteAvailability object with status=CLSD, direction as indicated in the RouteSegment BASELINE and at least one associated level.AirspaceLayer object(s) as available in the RouteSegment BASELINE shall be included in the TEMPDELTA Timeslice for each RouteSegment concerned. (question)

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-06

Note that in accordance with the AIXM Temporality Concept (see sections 3.4 and 3.5 of the Temporality document version 1.0), 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 and/or levels, the other times 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 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. Not included in the NOTAM text generation". This is based on the current NOTAM practice which consists of including in the NOTAM only the changed information and not explicitly including the static data that remains valid during the NOTAM applicability.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.

...