Versions Compared

Version Old Version 2 New Version 3
Changes made by

Andreea Perca (Deactivated)

Andreea Perca (Deactivated)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Data item

Description

AIXM mapping

airport designator

The published designator of the airport where the apron is located, used in combination with other elements in order to identify the apron portion concerned.

AirportHeliport.designator

airport name

The published name of the airport where the apron is located, used in order to identify the apron(s) and/or apron portion(s) concerned.

AirportHeliport.name

apron name

The published name of the apron concerned. This information is used in combination with the airport designator/name in order to identify the affected  apron(s) and/or apron portion(s)

Apron.name

apron portion relative locationA textual description of the area to be closed ApronElement.annotation with propertyName="extent" and purpose="REMARK"
apron portion closed geometryThe coordinates defining the apron portion to be closed.ApronElement.extent/ElevatedSurface
closed lengthThe length of the apron portion to be closedApronElement.length
closed widthThe width of the apron portion to be closedApronElement.width

closure reason

The reason for the apron portion closure.

ApronElement/ApronAreaAvailability.annotation with propertyName="operationalStatus" and purpose="REMARK". Note that the property "warning" of the ApronAreaAvailability 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 apron closure starts. This might be further detailed in a "schedule".

ApronElement/ApronTimeSlice/TimePeriod.beginPosition, Event/EventTimeSlice.validTime/timePosition and Event/EventTimeSlice.featureLifetime/beginPosition

end time

The end date & time when the apron closure ends.

ApronElement/ApronTimeSlice/TimePeriod.endPosition and Event/EventTimeSlice.featureLifetime/endPosition also applying the rules for {{Events with estimated end time}}

schedule (question)

A schedule might be provided, in case the apron is effectively closed according to a regular timetable, within the overall closure period.

ApronElement/ApronAreaAvailability/Timesheet/...according to the rules for {{Schedules}}

note

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

ApronElement/ManoeuvringAreaAvailability.annotation according to the rules for encoding annotations

...

Identifier

Data encoding rule

ER-01

The temporary closure of an apron or portion thereof shall be encoded as:

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

    a TimeSlice of type BASELINE for the ad-hoc ApronElement feature, for which the

    "event:theEvent" property

    “event:theEvent”property points to the Event instance created above;

  • a TimeSlice of type TEMPDELTA TimeSlice for each the affected Apron feature for on which the above ApronElement describesPartOf (associatedApron)ApronElement resides, for which the "event:theEvent" property points to the Event instance created above;

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

  • The application shall support the operator in order to automatically select the ApronElements that are concerned, as much as possible with a graphical view. When no graphical view is available, the application would need to analyze the closed apron portion input provided by the operator in comparison with the baseline data descriptions.If the operator specifies that the portion concerned is spread across multiple ApronElements, then the application shall automatically select the portions highlighted. 
ER-02In case of complete apron closure, one ApronAreaAvailability element having ApronElement BASELINE TimeSlice shall ApronAreaAvailability with operationalStatus=CLOSED shall be included in each Apron TEMPDELTA.
ER-03In case of apron portion closure, one ApronAreaAvailability element having operationalStatus=CLOSED shall be included in each ApronElement TEMPDELTA selected to be closed.
ER-04

In case of apron portion closure, a TEMPDELTA TimeSlice for the affected Apron feature for which the ApronElement describesPartOf (associatedApron) shall be created and shall have Apron.availability/ApronAreaAvailability.operationalStatus=LIMITED.

ER-05

If the closure is "except for" flight and/or aircraft categories, all specified exceptions shall be encoded as ApronAreaUsage child elements with:

  • either type=PERMIT, if there is no prior permission requirement;
  • or type=CONDITIONAL, if a prior permission requirement was specified. Note that this implies that a "closed" apron can still allow certain particular operations.

ER-06

If a unique flight or aircraft are specified as being excepted, they shall be encoded as one ConditionCombination with logicalOperator="NONE".

ER-07

Each pair of flight and aircraft conditions specified as being excepted shall be encoded as one ConditionCombination with logicalOperator="AND".

ER-08

If the "other combination" branch is used, then a root ConditionCombinations element shall be encoded having logicalOperator="OR" and each pair of flight/aircraft included as a sub-condition (with logicalOperator="AND", see ER-07).

ER-09

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 ApronAreaAvailability of all affected Apron and/or ApronElement TEMPDELTA Timeslice(s). See the rules for Event Schedules. (e.g. If a ApronElement is closed based on a schedule, its associatedApron TEMPDELTA shall have the same associated schedule (question))

ER-10

In accordance with the AIXM Temporality Concept, the ApronAreaAvailability elements included in the TEMPDELTA completely replace all the BASELINE ApronAreaAvailability information, during the TEMPDELTA time of applicability. Therefore, if the closure only concerns certain times, then the other times, when the Apron and/or ApronElement eventually remains subject to the availability conditions of the Baseline data, shall be explicitly included in the TEMPDELTA. The calculation of the necessary additional ApronAreaAvailability elements to be included in the TEMPDELTA shall be automatically done by the applications implementing this specification.

All ApronAreaAvailability elements that are copied from the BASELINE data for completeness sake shall get an associated Note with purpose=REMARK and the text="Baseline data copy. Not included in the NOTAM text generation". This is based on the current NOTAM practice which consists of including in the NOTAM only the changed information and not explicitly including the static data that remains valid during the NOTAM applicability.It is recommended that the input interface provides a "calendar" view of each apron element closure, enabling the operator to graphically check the availability at different times, such as in the example below:  

Image Removed

In the calendar view, the Baseline information that remains valid during the Event validity time shall be visibly identified from the information that is specific to the Event, for example by using a different colour fill pattern.

ER-11

If there exists aircraft stands on the closed Apron and/or ApronElement and if the apron closure makes the aircraft stand unavailable, then a consequence STAND.CLS scenario shall also be encoded for the relevant AircraftStand feature and shall include a reference to the current event with role 'causeEvent'. (STAND.CLS under development)

Examples

...

ApronElement BASELINE TimeSlice shall have associatedApron xlink:href the Apron on which is located (as selected by the operator)
ER-04

Apron TEMPDELTA shall have RunwayDirection.availability/ManoeuvringAreaAvailability.operationalStatus=LIMITED

Examples

under development