Versions Compared

Version Old Version 8 New Version 9
Changes made by

Andreea Perca (Deactivated)

Andreea Perca (Deactivated)

Saved on

Key

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

Definition

...

...

Identifier

Data encoding rule

ER-01

The temporary closure of a runway shall be encoded as:

  • a new Event with a BASELINE Timeslice (encoding=”DIGITAL”, scenario=”RWY.CLS”, version=”2.0”) for which a PERMDELTA TimeSlice may also be provided and

  • a TimeSlice of type TEMPDELTA for each affected RunwayDirection feature, for which the "event:theEvent" property points to the Event instance created above. Note that in case a full runway is concerned by the closure, then a TEMPDELTA shall be encoded for each of its RunwayDirection features.

ER-02

One ManoeuvringAreaAvailability element having operationalStatus=CLOSED shall be included in each RunwayDirection TEMPDELTA.

ER-03

If the runway is "closed except for" specified operations, flight and/or aircraft categories, all specified excepted operations shall be encoded as RunwayDirection.availability/ManoeuvringAreaAvailability.usage/ManoeuvringAreaUsage child elements with:

  • either type=PERMIT, if there is no prior permission requirement;

  • or type=CONDITIONAL, if a prior permission requirement was specified. Note that this implies that a "closed" runway can still allow certain particular operations.

ER-04

For every ManoeuvringAreaUsage encoded, the aixm:operation shall be specified.

ER-05

If PPR time is specified, the uom attribute shall also be specified.

ER-06

If a unique flight or aircraft are specified as being excepted, they shall be encoded as one ConditionCombination with logicalOperator="NONE".

ER-07

Each pair of flight and aircraft conditions specified as being excepted shall be encoded as one ConditionCombination with logicalOperator="AND".

ER-08

If the "other combination" branch is used, then a root ConditionCombination element shall be encoded having logicalOperator="OR" and each pair of flight/aircraft included as a subCondition (with logicalOperator="AND", see ER-07).

ER-09

If the runway closure is limited to a discrete schedule within the overall time period between the "start time" and the "end time", then this shall be encoded using as many as necessary timeInterval/Timesheet properties for the ManoeuvringAreaAvailability of the RunwayDirection TEMPDELTA Timeslice. See the rules for Event Schedules.

ER-10

In accordance with the AIXM Temporality Concept, the ManoeuvringAreaAvailability elements included in the TEMPDELTA completely replace all the BASELINE ManoeuvringAreaAvailability information, during the TEMPDELTA time of applicability. Therefore, if the closure only concerns certain times, then the other times, when the runway eventually remains subject to the availability conditions of the Baseline data, shall be explicitly included in the TEMPDELTA. The calculation of the necessary additional ManoeuvringAreaAvailability elements to be included in the TEMPDELTA shall be automatically done by the applications implementing this specification.

All ManoeuvringAreaAvailability 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" view of each runway direction closure, enabling the operator to graphically check the availability at different times, 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.

Examples