Versions Compared

Version Old Version 38 New Version 39
Changes made by

WOJTOWICZ Aleksander

POROSNICU Eduard

Saved on

Key

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

Definition

...

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. When this is the case, the number of the encoding rule is mentioned in the data validation rule.

Identifier

Data encoding rule

ER-01

The temporary runway portion closure shall be encoded as:

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

  • a TimeSlice of type BASELINE for the ad-hoc RunwayElement feature, for which the “event:theEvent” property points to the Event instance created above;

ER-02

RunwayElement BASELINE TimeSlice shall have associatedRunway xlink:href the Runway element on which is located.

ER-03

RunwayElement BASELINE TimeSlice shall have RunwayElement.availability/ManoeuvringAreaAvailability.operationalStatus=CLOSED.

ER-04

The description of the extent of the closed portion shall be encoded in a RunwayElement BASELINE Timeslice as an annotation with propertyName="extent" and purpose="DESCRIPTION"

ER-05

If runway portion 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 RunwayElement BASELINE Timeslice. See the encoding rules for {{Schedules}}.

ER-06

If the temporary RunwayElement overlaps with the position of a RunwayDirection's centreline points, then a consequence RCP.CHG scenario shall be encoded for the relevant RunwayCentrelinePoints(s) which shall include a reference to the current event with role “causeEvent”.

ER-07

If the temporary RunwayElement is impacting the declared distances of a RunwayDirection, then a consequence RDD.CHG scenario shall be encoded for the relevant RunwayDirection which includes a reference to the current event with role “causeEvent”.

ER-08

The system shall automatically identify the FIR where the AerodromeHeliport is located. This shall be coded as corresponding concernedAirspace property in the Event

ER-09The AirportHeliport concerned by the closure shall also be coded as concernedAirportHeliport property in the Event.

Examples

Following coding examples can be found on GitHub (links attached):

...