[RWE.CLS] Runway portion - closure

Definition

The temporary closure of a portion of a runway towards one of its ends (for example: work in progress at one runway end).

Notes:

this scenario covers the closure of a runway portion at the beginning or the end of the runway;
this scenario does not cover the closure of a permanent baseline runway portion;
this scenario does not cover the eventual change of the runway centerline points as a consequence for portion closure. For this situation refer to RCP.CHG scenario;
this scenario does not cover the eventual change of the runway centerline points as a consequence for portion closure. For this situation refer to RDD.CHG scenario;
this scenario does not cover the closure of a runway portion except for operations;
this scenario does not cover the change of the RWY width;
this scenario does not cover the unavailability of a turning bay at the end of the runway. For this situation refer to APN.CLS scenario (scenario not yet available, work in progress);
this scenario covers only closures which include either the start or the end of a runway (no middle sections)

Event data

The following diagram identifies the information items that are usually provided by a data originator for this kind of event.

EBNF Code

input = "airport designator" ["airport name"] "runway direction" ["runway surface composition"] \n
"runway section closed" "closed length" \n
"start time" "end time" ["schedule"] {note}.

The table below provides more details about each information item contained in the diagram. It also provided the mapping of each information item within the AIXM 5.1.1 structure. The name of the variable (first column) is recommended for use as label of the data field in human-machine interfaces (HMI).

Data item	Description	AIXM Mapping
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 direction	The published designator of the runway direction concerned. This information is used in combination with the airport designator/name in order to identify the runway affected by the portion closure.	RunwayDirection.designator
runway section closed	The indication of the portion of the runway to be closed. The available options should be only “first” or “last” having as reference the runway direction for which the event is concerned.	RunwayElement.type
closed length	The length of the runway element portion to be closed.	RunwayElement.length
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

Assumptions for baseline data

It is assumed that following BASELINE TimeSlices covering the entire duration of the event exist and have been coded as specified in the Coding Guidelines for the (ICAO) AIP Data Set:

AirportHeliport BASELINE as specified in the Basic Data for Airport/Heliport,
Runway BASELINE according to the coding rules for Basic Data for Runway; and
RunwayDirection BASELINE according to the coding rules for Basic Data Runway Direction

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; a TimeSlice of type TEMPDELTA for the affected RunwayDirection feature(s), for which the "event:theEvent" property points to the Event instance created above, as described below.
ER-02	Only the following values shall be used for RunwayElement.type: OTHER:FIRST OTHER:LAST
ER-03	RunwayElement BASELINE TimeSlice shall have associatedRunway xlink:href same as the RunwayDirection element used to define the runway direction affected by the portion closure.
ER-04	RunwayElement BASELINE TimeSlice shall have RunwayElement.availability/ManoeuvringAreaAvailability.operationalStatus=CLOSED.
ER-05	A RunwayDirection TEMPDELTA shall be created for the RunwayDirection used to define the runway direction affected by the portion closure and shall have RunwayDirection.availability/ManoeuvringAreaAvailability.operationalStatus=LIMITED.
ER-06	The RunwayDirection TEMPDELTA created under ER-05 shall have an annotation with purpose=DESCRIPTION and note with the decoding of the following elements: EBNF Code Expand source note = "RunwayElement.type" "RunwayElement.length" "RunwayElement.length.uom" "closed". e.g. "First 300m closed" Notes: RunwayElement.type can be only "first" and "last", according to ER-02. This annotation will not be used for the decoding. It is intended only as a note explaining the reason for the "LIMITED" status.
ER-07	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-08	If the temporary baseline RunwayElement has type=OTHER:FIRST 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-09	If the temporary baseline RunwayElement has type=OTHER:LAST then a consequence RDD.CHG scenario shall be encoded for the relevant RunwayDirection which include a reference to the current event with role “causeEvent”

Examples

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