[2.0] [APE.LIM] Apron portion - usage limitation change

Definition

The temporary change of usage limitation of a portion of an area intended to accommodate aircraft for purposes of loading or unloading passengers, mail or cargo, fueling, parking or maintenance. 

Notes:

  • this scenario includes the change of usage limitation of a portion of an apron. It is assumed that the apron portion does not exist in the baseline data, and has to be created for the event;
  • this scenario does not include closure of apron portions, defined by reference to intersection with other airport surfaces. For this refer to APE.CLS scenarios.

Event data

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 used more than once.

EBNF Code
input = "airport designator" ["airport name"] "apron name" \n
"apron portion limitation geometry" "location and extent description"  \n
("conditional for" | "closed, except for" |  "prohibited for" | "allowed for")
(["aircraft"] ["flight"]) {["aircraft"] ["flight"]} ["PPR time" ["PPR details"]] \n
["reason"] "start time" "end time" [schedule] \n
[note].

The table below provides more details about each information item contained in the diagram. It also provides the mapping of each information item within the AIXM 5.1.1 structure. The name of the variable (first column) is recommended for use as label of the data field in human-machine interfaces (HMI).

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

The coordinates defining the apron portion affected by the limitation.


ApronElement.extent/ElevatedSurface.posList

location and extent description

Textual description of the limitation-affected apron portion location and extent. 

ApronElement.annotation with propertyName='extent' and purpose='DESCRIPTION'
conditional forThe description of one or more operations, which is permitted under special conditions, usually a prior permission requirement

ApronElement.availability.ApronAreaAvailability.operationalStatus with value 'LIMITED' and 

ApronElement/..Availability/..Usage.type with value 'CONDITIONAL'

closed, except forApron portion is closed, except for operations explicitly identified in the input data.

ApronElement.availability.ApronAreaAvailability.operationalStatus with value 'LIMITED' and 

ApronElement/..Availability/..Usage.type with value 'RESERV'

prohibited forThe description of one or more operations that are prohibited for during the event duration.

ApronElement.availability.ApronAreaAvailability.operationalStatus with value 'LIMITED' and 

ApronElement/..Availability/..Usage.type with value 'FORBID'

additionally allowed for

The description of one or more additional operations that are available for a specific purpose during the event duration.

ApronElement.availability.ApronAreaAvailability.operationalStatus with value 'OTHER:EXTENDED' and 

ApronElement/..Availability/..Usage.type with value 'PERMIT'

aircraft

The description of one or more aircraft (such as "helicopter") types are permitted or prohibited (depending on the limitation type) during the event duration.

ApronElement/..Availability/..Usage/..selection/..AircraftCharacteristics 

Only the following AircraftCharacteristics properties are allowed to be used in this scenario: type, engine, wingSpan, wingSpanInterpretation, weight, weightInterpretation.

flight

The description of one or more type of flight categories (such as "emergency") that are permitted or prohibited (depending on the limitation type) during the event duration.

ApronElement/..Availability/..Usage/..selection/..FlightCharacteristics.

Only the following FlightCharacteristics properties are allowed to be used in this scenario: type, rule, status, military, origin, purpose.

PPR timeThe value (minutes, hours, days) of the prior permission request associated with a permitted operation.ApronElement/ApronAreaAvailability/..Usage.priorPermission with uom attribute specified
PPR detailsAdditional information concerning the prior permission requirement.ApronElement/ApronAreaAvailability/..Usage.annotation with propertyName='priorPermission' and purpose='REMARK'

reason

The reason for the apron portion usage limitation.

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

start time

The effective date & time when the apron portion limitation starts. This might be further detailed in a "schedule".

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

end time

The end date & time when the apron portion limitation ends.

ApronElement/ApronTimeSlice/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 apron portion's usage is effectively limited according to a regular timetable, within the overall limitation period.

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

note

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

ApronElement/ApronAreaAvailability.annotation with purpose='REMARK'

Assumptions for baseline data

For AirportHeliport for which ApronElement limitation is to be reported, it is assumed that AirportHeliport BASELINE Timeslice, covering the entire duration of the event exists and have been coded as specified in the Coding Guidelines for the (ICAO) AIP Data Set. In addition the information about the Apron, for which an impacted ApronElement describesPartOf, already exists in the form of a Apron BASELINE TimeSlice, which contains as a minimum:

  1. a name, and
  2. an association with the AirportHeliport;

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 usage limitation of an apron portion shall be encoded as:

  • a new Event with a 'BASELINE' TimeSlice (scenario='APE.LIM', 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;

ER-02ApronElement BASELINE TimeSlice shall have associatedApron@xlink:href the Apron on which is located (as selected by the operator)
ER-03The location and extent description shall be encoded in free text as an ApronElement.annotation with propertyName='extent' and purpose='DESCRIPTION'

ER-04

The ApronElement BASELINE TimeSlice shall have ApronAreaAvailability with 'operationalStatus' equal to

  • 'LIMITED', if the apron portion usage is "conditional for", "closed, except for", "prohibited for";
  • 'OTHER:EXTENDED', if the apron portion usage is "allowed for".
ER-05

If the apron portion usage is "conditional for" specified operations, flight and/or aircraft categories, then all specified limitations shall be encoded as ApronAreaUsage child elements with type='CONDITIONAL'.

ER-06

If the apron portion is "closed, except for" specified operations, flight and/or aircraft categories, then all specified limitations shall be encoded as ApronAreaUsage child elements with type='RESERV'.

ER-07

If the apron portion usage is "prohibited for" specified operations, flight and/or aircraft categories, all specified limitations shall be encoded as ApronAreaUsage child elements with type='FORBID'.

ER-08If the apron portion usage is "allowed for" specified operations, flight and/or aircraft categories, all specified limitations shall be encoded as ApronAreaUsage child elements with type='PERMIT'.
ER-09

The "aircraft-flight" branch can be used more than once. If this the case, then a parent ConditionCombination with logicalOperator='OR' shall be coded first. Otherwise, this parent element is not necessary.

Then, each flight and/or aircraft combination shall be coded as a child ConditionCombination with logicalOperator equal to:

  • 'NONE' - if either a flight condition or aircraft condition is specified (but not both);
  • 'AND' - if both a flight condition and aircraft condition are specified.

ER-10

If PPR time is specified, the uom attribute shall also be specified.

ER-11If there exists aircraft stands on the ApronElement affected by a usage limitation and if the apron portion limitation makes the aircraft stand (partially) unavailable, then a consequence STAND.LIM scenario shall also be encoded for the relevant AircraftStand feature and shall include a reference to the current event with role 'causeEvent'.
ER-12The system shall automatically identify the FIR where the AirportHeliport is located. This shall be coded as corresponding concernedAirspace property in the Event
ER-13The AirportHeliport associated with the Apron with the area limitation shall also be coded as concernedAirportHeliport property in the Event.

Examples

Following coding examples can be found on GitHub (links attached):

  • to be generated