[2.0] [RWE.CLS] Runway portion - closure

Definition

The temporary closure of a portion of a runway.

Notes:

this scenario covers the closure of a runway portion described by its geometry (coordinates); It is assumed that the runway portion does not exist in the baseline data, and has to be created for the event;
this scenario does not cover the permanent closure of a runway portion;
this scenario does not cover the eventual change of the runway centerline points as a consequence for portion closure. When necessary, a consequence Event will be coded, using the RCP.CHG scenario;
this scenario does not cover the eventual change of the runway declared distances as a consequence for portion closure. When necessary, a consequence Event will be coded, using the RDD.CHG scenario;
this scenario does not cover the closure of a runway portion that does not affect the operations ("except for operations");
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;

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" | "runway direction") ["runway surface composition"] \n
"runway portion closed geometry" "extent closed" \n
"status=CLOSED" ["closure reason"] "start time" "end time" [schedule] \n
[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	The published designator of the 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 direction	The indication of the runway direction on which the portion closure has operational impact. 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 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
extent closed	A description of the extent of the closed portion.	RunwayElement.annotation with propertyName='extent' and purpose='DESCRIPTION'
status=CLOSED	The operational status of the runway element. In this scenario, it is only possible to indicate a complete closure.	RunwayElement/ManoeuvringAreaAvailability.operationalStatus
closure reason	The reason for the runway portion closure.	RunwayElement/ManoeuvringAreaAvailability.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

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, and
Runway BASELINE according to the coding rules for Basic Data for Runway.

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 (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 on which the closed portion 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.Note 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 might need to be coded for the relevant 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 might need to be coded for the relevant RunwayCentrelinePoint(s) 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-09	The 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):

Page tree