Page Comparison

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 portion input

The portion of a published taxiway, specified using intersection elements between that taxiway and other taxiways, runways, aprons or stands.

Note on closed taxiway portion input:

1. The application shall allow graphical display and selection of taxiway(s) and/or taxiway portion(s) to be closed;

2. The HMI application should support the operator in identifying all relevant taxiways, taxiways portions and other elements that are affected by the closure and have an impact on operations. As a general rule, if an intersection has to be closed, the Taxiways and/or TaxiwayElements linked to this intersection shall also be closed up to the intersection.

3. The application shall support the operator in avoiding cul-de-sac/dead-end situations and warn on situations when other Taxiways and/or TaxiwayElements are leading to nowhere. The application shall suggest to either include them in the NOTAM or generate a new NOTAM, as appropriate. 
4. The operator shall be the one manually selecting all the portions to be closed. 

TaxiwayElement(s) identified as explained in the Data Encoding Rule ER-01. 

closure reason

The reason for the taxiway(s) and/or taxiway portion(s) closure.

Taxiway/ or TaxiwayElement/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/ or TaxiwayElement/TaxiwayTimeSlice/TimePeriod.beginPosition, Event/EventTimeSlice.validTime/beginPosition and Event/EventTimeSlice.featureLifetime/beginPosition

end time

The end date & time when the taxiway closure ends.

Taxiway/ or TaxiwayElement/TaxiwayTimeSlice/TimePeriod.endPosition, 
Event/EventTimeSlice.validTime/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 taxiway is effectively closed according to a regular timetable, within the overall closure period.

Taxiway/ or TaxiwayElement/ManoeuvringAreaAvailability/Timesheet/...according to the rules for {{Schedules}}

note

A free text note that provides further details concerning the taxiway closure.

Taxiway/ or TaxiwayElement/ManoeuvringAreaAvailability.annotation according to the rules for encoding annotations

ER-01

The temporary closure of a taxiway or portion thereof shall be encoded as:

• a new Event with a BASELINE TimeSlice (scenario=TWY.CLS, version=2.0), for which a PERMDELTA TimeSlice may also be provided; and
• in case of complete taxiway closure:
  • a TEMPDELTA TimeSlice for each affected Taxiway feature, for which the "event:theEvent" property points to the Event instance created above;
• in case of partial taxiway closure:
  • a TEMPDELTA TimeSlice for each affected TaxiwayElement feature, for which the "event:theEvent" property points to the Event instance created above;

Identification of the TaxiwayElements to be closed shall be done as follows:

• The application shall support the operator in order to automatically select the TaxiwayElements that are concerned with a graphical view. 
• With reference to Fig. 1 included in the “Assumptions for baseline data” further up in the document, if the operator specifies that the portion concerned is between intersections A/B and A/D, then the application shall automatically select the portions highlighted. By default, intersections are supposed to remain open, unless explicitly specified as closed.

First, all the BASELINE availability.ManoeuvringAreaAvailability (with operationalStatus=NORMAL), if present, shall be copied in the TEMPDELTA. 

Then, an additional availability.ManoeuvringAreaAvailability element having operationalStatus=CLOSED shall be coded in the Taxiway TEMPDELTA.

ER-05

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 of all affected Taxiway or TaxiwayElement TEMPDELTA Timeslice(s). See the rules for Event Schedules. 

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 shall also be encoded for the relevant Apron feature and shall include a reference to the current event with role 'causeEvent'. 

The system shall automatically identify the FIR where the AerodromeHeliport is located. This shall be coded as corresponding concernedAirspace property in the Event