The temporary displacement of a runway centreline point.
- this scenario covers the displacement of a runway centreline point for a single runway direction;
- this scenario does not cover the creation of a new runway centreline point, except for the "legacy coding case", where a new "start of take-off" point is created (see Note 2 below);
- this scenario covers only inward (i.e. down the runway) displacement of a runway centreline point;
- this scenario does not cover the situation when the runway centreline point is displaced according to a schedule;
Note 1: According to the coding guidelines for the ICAO AIP Data Set in AIXM 5.1/5.1.1 format, the departure declared distances are associated with a a RunwayCentrelinePoint with role START_RUN and the landing declared distance with another RunwayCentrelinePoint with role THR. There might be situations which will require both points to be displaced, e.g. if a RWY first portion is closed due to WIP. In this case, two separate RCP.CHG Events need to be coded. They can be children or consequences of the same parent Event.
Note 2: It might be the case for legacy systems that all declared distances are associated with one RunwayCentrelinePoint having role THR. This require special consideration which are marked in the text by the remark "legacy coding case". A detailed description of this situation can be found in the coding guidelines for the ICAO AIP Data Set - Declared Distances.
The following diagram identifies the information items that are usually provided by a data originator for this kind of event.
The table below provides more details about each information item contained in the diagram. It also provides 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).
The published designator of the airport where the runway is located, used in combination with other elements in order to identify the runway concerned.
The published name of the airport where the runway is located, used in combination with other elements in order to identify the runway concerned.
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 landing direction and its centreline point.
RunwayDirection.designator and RunwayCentrelinePoint.onRunway
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 in order to identify the runway concerned.
|runway centreline point designator||The designator of the RunwayCentrelinePoint which is temporary to be changed. The value is used in combination with the runway direction information in order to identify the RunwayCentrelinePoint concerned.|
|runway centreline point location|
The location of the runway centreline point which is temporary to be changed. The value is used in combination with the runway direction information in order to identify the RunwayCentrelinePoint concerned.
Note: The application should support the operator by allowing graphically display and selection of the runway centreline point to be affected by the event.
The value of the centreline point displacement from the start towards the centre of the runway.
Note: The displacement distance should always be provided from the start of the runway. If the baseline data contains a permanent displaced RunwayCentrelinePoint which needs to be temporary moved, the displacement distance provided should be considered from the start of the runway and not from its (baseline) displaced location.
RunwayCentrelinePoint.annotation with propertyName="location", purpose="DESCRIPTION" and note="(value of the centreline point displacement) (value of the distance uom)".
runway centreline point new position
The new lat/long position of the centreline point, if applicable.
runway centreline point new elevation
The new elevation of the centreline point, if applicable.
|new runway centreline point position||(legacy coding case) The location of a new temporary runway centreline point which represents the start of take-off run.||RunwayCentrelinePoint.location/ElevatedPoint.pos|
|new runway centreline point elevation||(legacy coding case) The elevation of the new centreline point, if applicable||RunwayCentrelinePoint.location/ElevatedPoint.elevation|
|new runway centreline point designator||(legacy coding case) The designator of a new temporary runway centreline point which represents the start of take-off run.||RunwayCentrelinePoint.designator|
The effective date & time when the runway centreline point displacement starts.
RunwayCentrelinePoint/ RunwayCentrelinePointTimeSlice/TimePeriod.beginPosition, Event/EventTimeSlice.validTime/ timePosition and Event/EventTimeSlice.featureLifetime/ beginPosition
The end date & time when the runway centreline point displacement ends.
A free text note that provides further details concerning the runway displaced centreline point.
RunwayCentrelinePoint.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;
RunwayDirection BASELINE according to the coding rules for Basic Data Runway Direction, and
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. To the maximum possible extent, the compliance with these encoding rules shall be verified with automatic data validation rules.
Data encoding rule
The temporary displacement of a runway centreline point shall be encoded as:
If the baseline RunwayCentrelinePoint has role='THR' or 'DISTHR', the RunwayCentrelinePoint TEMPDELTA shall have role="DISTHR".
If the "displacement distance" is provided, it shall be encoded in RunwayCentrelinePoint.annotation with propertyName="location", purpose="DESCRIPTION" and note="(value of the centreline point displacement) (value of the distance uom)".
Note: Current AIXM 5.1.1 would allow the coding using RunwayCentrelinePoint.associatedDeclareDistance/RunwayDeclaredDistance.type and RunwayCentrelinePoint.associatedDeclareDistance/RunwayDeclaredDistance.declaredValue/RunwayDeclaredDistanceValue.distance. However, this is not used here that there is no conflict with the decision to have the RDD scenario issuing a parallel TEMPDELTA for another property.
(legacy coding case) If the baseline RunwayCentrelinePoint has role equal-to "THR" or "DISTHR" or "START" and associatedDeclaredDistance with RunwayDeclaredDistance of type TORA, TODA, ASDA and LDA (or respectively TODAH, RTODAH, LDAH for helicopters) are associated with it, a new RunwayCentrelinePoint BASELINE TimeSlice with role="START_RUN" shall be created.
Note: This case is typical for legacy data, when all Declared Distances (TORA, TODA, ASDA, LDA or respectively TODAH, RTODAH, LDAH for helicopters) are associated with one RunwayCentrelinePoint. In this situation the point has two roles: one as landing threshold and one as departure threshold. In other words, there are two roles associated with the same point. There might be cases when the displacement affects only the landing thereshold, while the start of the take-off run remains in the same location. Therefore, in case of displacement, the operator needs to make the separation and create a new RunwayCentrelinePoint BASELINE for the hidden role. The application should support the operator by identifying the double-role of a point and provide him with the appropriate data input forms.
(legacy coding case) The new RunwayCentrelinePoint BASELINE TimeSlice shall contain the new runway centreline point position, new runway centreline point elevation and new runway centreline point designator, as provided by the operator.
|ER-06||(legacy coding case) The new RunwayCentrelinePoint BASELINE TimeSlice shall have onRunway xlink:href same as the baseline RunwayCentrelinePoint with role="THR".|
|ER-07||If the centreline point position is not provided, the RunwayCentrelinePoint TEMPDELTA (and BASELINE if created according to rule ER-04) shall contain aixm:location with xsi:nil="true" nilReason="unknown".|
If the baseline RunwayCentrelinePoint has associatedDeclaredDistance and if the RunwayCentrelinePoint displacement changes the declared distance, then a consequence RDD.CHG scenario shall also be coded for the relevant RunwayDeclaredDistances and shall include a reference to the current event with role 'causeEvent'.
(temporary rule until further scenarios are developed) If the centreline point new position is unknown, all baseline elements of the RunwayCentrelinePoint which contain a distance relative to the position of the centreline point (e.g. navaidEquipment) shall be included in the TEMPDELTA TimeSlice with xsi:nil="true" and nilReason="unknown". Otherwise, if the relative distances can be computed, they shall be included in the TimeSlice(s) accordingly.
Following coding examples can be found on GitHub (links attached):