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