Page Comparison

airport designator

The published designator of the airport where the runway is located, used in combination with other elements in order to identify the runway concerned.

AirportHeliport.designator

airport name

The published name of the airport where the runway is located, used in order to identify the runway concerned.

AirportHeliport.name

runway 

The published designator of the runway direction runway  concerned. This information is used in combination with the airport designator/name in order to identify the runway affected by the portion closure.

Runway.designator

runway surface composition

In cases where there are two runways with the same designator but different surfaces (for instance RWY 07/25, one concrete and the second gravel or grass), the surface composition needs to be provided.

Runway.surfaceProperties/SurfaceCaracteristics.composition

runway portion closed geometry

The coordinates defining the runway portion to be closed. 

RunwayElement.extent/ElevatedSurface

closure reason

The reason for the runway portion closure.

RunwayElement/ManoeuvringAreaAvailability.annotation with annotation with propertyName="'operationalStatus" ' and purpose="'REMARK"'. Note that the property "warning" of the ManoeuvringAreaAvailability class is not used here because it represents a reason for caution when allowed to operate on the apron, not a reason for a closure.

start time

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

RunwayElement/ RunwayElementTimeSlice.validTime/TimePeriod.beginPosition,

Event/EventTimeSlice.validTime/TimePeriod.beginPosition,

RunwayElement/ RunwayElementTimeSlice.featureLifetime/beginPosition,

and Event/EventTimeSlice.featureLifetime/beginPosition

end time

The end date & time when the runway portion closure ends.

RunwayElement/ RunwayElementTimeSlice.validTime/TimePeriod.endPosition,

Event/EventTimeSlice.validTime/ TimePeriod.endPosition,

RunwayElement/ RunwayElementTimeSlice.featureLifetime/endPosition,

and Event/EventTimeSlice.featureLifetime/endPosition

also applying the rules for {{ Events with estimated end time}}.

schedule

A schedule might be provided, in case the runway portion is effectively closed according to a regular timetable, within the overall closure period.

RunwayElement/ManoeuvringAreaAvailability/Timesheet/...according to the rules for {{Schedules}}

note

A  free text note that provides further details concerning the runway portion closure.

RunwayElement.annotation according to the rules for encoding annotations

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“event:theEvent” theEvent” property points to the Event instance created above;

ER-02

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

ER-03

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

The description of the extent of the closed portion shall be encoded in a RunwayElement BASELINE Timeslice as an annotation.Note with propertyName="'extent" and ' 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 might need to be encoded coded for the relevant RunwayCentrelinePoints RunwayCentrelinePoint(s), which shall include a reference to the current event with role name “causeEvent”.

ER-07

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

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