Page tree
Skip to end of metadata
Go to start of metadata

Definition

The temporary change of one or more declared distances for one runway direction. 

Notes:

  • this scenario covers the change of one or more runway declared distances;
  • this scenario does not cover the change of the start point of the declared distances measurement. For this refer to RCP.CHG scenario. 

Note : 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 or DISTHR. 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.

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 centreline point designator" | "runway centreline point location") "declared distance type" "declared distance value" {"declared distance type" "declared distance value"} {("runway centreline point designator" | "runway centreline point location") "declared distance type" "declared distance value" {"declared distance type" "declared distance value"}} \n
"start time" "end time" [schedule] {note}.

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).

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 and the concerned landing direction.

RunwayDirection.designator 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.

Runway.SurfaceCaracteristics.composition

runway centreline point designator

The designator of the RunwayCentrelinePoint to which the declared distances are associated. The value is used to identify the RunwayCentrelinePoint with which the affected declared distances are associated.

Note: The application should support the operator by displaying all baseline RunwayDeclaredDistance associated with the selected point.

RunwayCentrelinePoint.designator

runway centreline point location

The location of the RunwayCentrelinePoint to which the declared distances are associated. The value is used to identify the RunwayCentrelinePoint with which the affected declared distances are associated.

Note: The application should support the operator by allowing graphically display and selection of the runway centreline point to be affected by the event. Furthermore, the application should support the operator by displaying all baseline RunwayDeclaredDistance associated with the selected point.

RunwayCentrelinePoint.location/ElevatedPoint.pos

declared distance type

The type of declared distance.

Note: the coding guidelines for the ICAO AIP Data Set - Declared Distances different declared distance types can be associated to different centerline points. The application shall support in the HMI the operator by providing the baseline values and asking the operator to indicate which and by what have have been modified.

RunwayCentrelinePoint/RunwayDeclaredDistance.type

declared distance value

The value of the declared distance.

RunwayCentrelinePoint/RunwayDeclaredDistance/RunwayDeclaredDistanceValue.distance

start time

The effective date & time when the temporary declared distances start. This might be further detailed in a "schedule".

RunwayCentrelinePoint/ RunwayCentrelinePointTimeSlice/ TimePeriod.beginPosition, Event/EventTimeSlice.validTime/ timePosition and Event/EventTimeSlice.featureLifetime/ beginPosition

end time

The effective date & time when the temporary declared distances end.

RunwayCentrelinePoint/ RunwayCentrelinePointTimeSlice/ TimePeriod.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 temporary declared distances are according to a regular timetable, within the overall period.

RunwayCentrelinePoint/RunwayDeclaredDistance/ RunwayDeclaredDistanceValue/Timesheet/...according to the rules for {{Schedules}}

note

A  free text note that provides further details concerning the temporary change.

RunwayCentrelinePoint/RunwayDeclaredDistance.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:

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 changes of declared distances shall be encoded as:

  • a new Event with a BASELINE TimeSlice (encoding=DIGITAL, scenario=RDD.CHG, version=2.0), for which a PERMDELTA TimeSlice may also be provided; and
  • TEMPDELTA TimeSlices for the affected RunwayCentrelinePoint features identified and have associatedDeclaredDistances, for which the "event:theEvent" property points to the Event instance created above, as described below.
ER-02RunwayDeclaredDistance object(s) affected by an Event shall be encoded in TEMPDELTA TimeSlice(s) of the RunwayCentrelinePoint feature(s) with which is(are) associated in the baseline, with the exception described in Rule ER-03 below.
ER-03(legacy coding case) If the Event is a consequence of a THR.CHG Event based on legacy baseline data (i.e.one RunwayCentrelinePoint having role=THR and all Declared Distances (TORA, TODA, ASDA, LDA or respectively TODAH, RTODAH, LDAH for helicopters) are associated with it), than the RunwayDeclaredDistance of type equal-to TORA, TODA and ASDA shall be encoded as a BASELINE TimeSlice of the new RunwayCentrelinePoint created under Rule ER-03 of THR.CHG scenario.
ER-04If any RunwayDeclaredDistance does not have the RunwayDeclaredDistance.type and RunwayDeclaredDistanceValue.distance value changed by the Event, it shall get an associated Note with purpose=REMARK and the text="Baseline data copy. Not included in the NOTAM text generation". This is based on the current NOTAM practice which consists of including in the NOTAM only the changed information and not explicitly including the static data that remains valid during the NOTAM applicability.

ER-05

If the change of declared distances 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 RunwayDeclaredDistanceValue timeInterval/Timesheet properties for each RunwayDeclaredDistanceValue. See the  general rules for coding schedules.

In accordance with the AIXM Temporality Concept, the RunwayDeclaredDistance associated with the TEMPDELTA completely replaces all the BASELINE RunwayDeclaredDistance information, during the TEMPDELTA time of applicability. Therefore, if the change only concerns certain times and/or levels, the other times and/or levels, when the declared distances eventually remains with the same status as in the Baseline data, shall be explicitly included in the TEMPDELTA, as explained in the general rules for coding schedules.

The calculation of the necessary additional RunwayDeclaredDistanceValue elements to be included in the TEMPDELTA shall be automatically done by the applications implementing this specification. All RunwayDeclaredDistanceValue elements that are calculated from the BASELINE data for completeness sake shall get an associated Note with purpose=REMARK and the text="Baseline data copy. Not included in the NOTAM text generation". This is based on the current NOTAM practice which consists of including in the NOTAM only the changed information and not explicitly including the static data that remains valid during the NOTAM applicability.

ER-06

If the change of declared distances is limited to a discrete schedule, all instances of RunwayDeclaredDistance which do not have an associated Note with purpose=REMARK and the text="Baseline data copy. Not included in the NOTAM text generation" shall have the same associated schedule for each RunwayDeclaredDistanceValue.

(Rationale: all declared distances changed by the event shall have the same associated schedule. Those declared distances that keep the same values should not have any schedule associated at all)

Examples

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

  • No labels