Definition
...
Data item | Description | AIXM mapping |
|---|---|---|
airport designator | The published designator of the airport where the taxiway is located, used in combination with other elements in order to identify the taxiway(s) and/or taxiway portion(s) concerned. | AirportHeliport.designator |
airport name | The published name of the airport where the taxiway is located, used in order to identify the taxiway(s) and/or taxiway portion(s) concerned. | AirportHeliport.name |
taxiway designator | The published designator of the taxiway concerned. This information is used in combination with the airport designator/name in order to identify the affected taxiway(s) and/or taxiway portion(s) | Taxiway.designator |
closed taxiway description | In case of a partial closure, a textual description of that taxiway portion concerned should be provided | Taxiway.availability.ManoeuvringAreaAvailability.annotation and purpose='DESCRIPTION' (see ER-0503) |
closed taxiway element | In case of both a partial and a total closure, the exact geometry of the closed taxiway portion should be precisely identified by specifying the concerned taxiway elements
| TaxiwayElement(s) identified as explained in the Data Encoding Rule ER-01. |
| status=CLOSED | The operational status of the taxiway. In this scenario, it is only possible to indicate a complete closure. | Taxiway.availability.ManoeuvringAreaAvailability.operationalStatus and TaxiwayElement.availability.ManoeuvringAreaAvailability.operationalStatus |
closure reason | The reason for the taxiway(s) and/or taxiway portion(s) closure. | Taxiway.availability.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 taxiway, not a reason for a closure. |
start time | The effective date & time when the taxiway closure starts. This might be further detailed in a "schedule". | Taxiway/TaxiwayTimeSlice/TimePeriod.beginPosition, TaxiwayElement/TaxiwayElementTimeSlice/TimePeriod.beginPosition, Event/EventTimeSlice.validTime/beginPosition and Event/EventTimeSlice.featureLifetime/beginPosition |
end time | The end date & time when the taxiway closure ends. | Taxiway/TaxiwayTimeSlice/TimePeriod.endPosition, TaxiwayElement/TaxiwayTimeSlice/TimePeriod.endPosition, |
schedule | A schedule might be provided, in case the taxiway is effectively closed according to a regular timetable, within the overall closure period. | Taxiway.availability.ManoeuvringAreaAvailability/Timesheet/... and TaxiwayElement.availability.ManoeuvringAreaAvailability/Timesheet/...according to the rules for Schedules |
note | A free text note that provides further details concerning the taxiway closure. | Taxiway.availability.ManoeuvringAreaAvailability.annotation with purpose='REMARK' |
...
- the information about each Taxiway concerned already exists in the form of a Taxiway BASELINE TimeSlice, which contains as a minimum:
- designator,
type (ex: EXIT, FASTEXIT, etc), and
association with the AirportHeliport;
- If taxiway portions are concerned, it is assumed that they are encoded in BASELINE TaxiwayElements, including their horizontal extent (geometry) to enable graphical selection.
- It is assumed that the following principle has been followed for the encoding of BASELINE Taxiway.availability and TaxiwayElement.availability data (as available in the BASELINE data):
- the operationalStatus has the value 'NORMAL' (meaning that the facility operates with nominal parameters) for all Taxiway.availability and/or TaxiwayElement.availability that are part of the BASELINE data;
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 closure of a taxiway or portion thereof shall be encoded as:
Important Note: the application shall support the operator in order to automatically select the TaxiwayElements that are concerned with a graphical view, as indicated in the figure below. By default, intersections are supposed to remain open, unless explicitly specified as closed.
|
| ER-02 | First, all the BASELINE availability.ManoeuvringAreaAvailability (with operationalStatus='NORMAL'), if present, shall be copied in the Taxiway and TaxiwayElement (if applicable) 'TEMPDELTA'. (see Usage limitation and closure scenarios). Then:
|
ER-03 | The textual description of the taxiway closed portion, if provided, shall be encoded as part of the Taxiway TEMPDELTA as availability.ManoeuvringAreaAvailability.annotation and purpose='DESCRIPTION'
|
ER-0604 | If the 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 (that have operationalStatus='CLOSED'/'LIMITED') of all affected Taxiway or and TaxiwayElement TEMPDELTA Timeslice(s) . See the rules for Event Schedules. |
| ER-0705 | If there exists a single Taxiway leading to an Apron and/or ApronElement and if the Taxiway closure makes the Apron unavailable, then a consequence APN.CLS scenario CLS scenario shall also be encoded for the relevant Apron feature and shall include a reference to the current event with role 'causeEvent'. |
| ER-0806 | The system shall automatically identify the FIR where the AerodromeHeliport AirportHeliport is located. This shall be coded as corresponding concernedAirspace property in the Event |
| ER-0907 | The AirportHeliport concerned by the closure shall also be coded as concernedAirportHeliport property in the Event. |
...