Versions Compared

Version Old Version 16 New Version 17
Changes made by

Andreea Perca (Deactivated)

Andreea Perca (Deactivated)

Saved on

Key

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

...

The following diagram identifies the information items that are usually provided by a data originator for this kind of event. Note that the flight and/or aircraft categories branch is optional, but can be more than once.

Image RemovedImage Added

Code Block
titleEBNF Code
collapsetrue
input = "airport designator" ["airport name"] "apron name" \n
("apron portion closed geometry" | "apron portion relative location" "closedand length"extent description"closed width") \n
["closure reason"] "start time" "end time" \n
{note}.

...

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 closed geometry

The coordinates defining the apron portion to be closed.

→ not for the text NOTAM.


ApronElement.extent/ElevatedSurface.posList

location and extent description

Textual description of the closed portion location and extent. 

→ to be used for text NOTAM.

ApronElement.annotation with propertyName="extent" and purpose="DESCRIPTION"

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

A schedule might be provided, in case the apron portion 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.annotation according to the rules for encoding annotations

...

Identifier

Data encoding rule

ER-01

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

  • a new Event with a BASELINE TimeSlice (encoding=DIGITAL, scenario=APE.CLS, version=2.0), for which a PERMDELTA TimeSlice may also be provided; and

  • a TimeSlice of type BASELINE for the ad-hoc ApronElement feature, for which the “event:theEvent”property points to the Event instance created above;

    a TimeSlice of type TEMPDELTA for the affected Apron feature on which the ApronElement resides, for which the "event:theEvent" property points to the Event instance created above. 

ER-02ApronElement BASELINE TimeSlice shall have ApronAreaAvailability with operationalStatus=CLOSED.
ER-03ApronElement BASELINE TimeSlice shall have associatedApron xlink:href the Apron on which is located (as selected by the operator)
ER-04The apron portion relative location The location and extent description shall be encoded in free text as an ApronElement.annotation with propertyName="extent" and purpose="DESCRIPTION"
ER-05

A TimeSlice of type TEMPDELTA shall be created for the Apron on which the ApronElement resides and have Apron.availability/ApronAreaAvailability.operationalStatus=LIMITED

ER-06If 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 the affected ApronElement TEMPDELTA Timeslice(s). See the rules for Event Schedules. 
ER-0706If there exists aircraft stands on the closed ApronElement and if the apron portion 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'.

...