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