Versions Compared

Version Old Version 10 New Version 11
Changes made by

POROSNICU Eduard

WOJTOWICZ Aleksander

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: typo in FASTEXIT corrected

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

status=CLOSEDThe operational status of the taxiway. In this scenario, it is only possible to indicate a complete closure.Taxiway/ or TaxiwayElement/ManoeuvringAreaAvailability.operationalStatus

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

...

  1. the information about the Taxiway already exists in the form of a Taxiway BASELINE TimeSlice, which contains as a minimum:
    1. a designator,

    2. a type (ex: EXIT, FASTEXTFASTEXIT, etc),  and

    3. an association with the AirportHeliport;

  2. If taxiway portions are concerned, it is assumed that they are encoded in BASELINE TaxiwayElements as suggested in the following diagram:
     
    Fig.1 - Encoding of TaxiwayElements

  3. It is assumed that each TaxiwayElements BASELINE have an annotation with purpose="OTHER:NOTAM_DESCRIPTION" and note describing their location as depicted below:
     
    Fig. 2 - Encoding of TaxiwayElement description 

    E.g. 
    * a TaxiwayElement of type INTERSECTION would have a description such as “intersection TWY A and TWY B”, 
    * a TaxiwayElement of type NORMAL would have a description such as "between RWY 08L/26R and TWY J".

...