Versions Compared

Old Version 21

changes.mady.by.user EDUARD POROSNICU

Saved on

compared with

New Version Current

changes.mady.by.user EDUARD POROSNICU

Saved on

Key

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

...

Code Block
titleEBNF Code
collapsetrue
input = "airport designator" ["airport name"] ("apron name") {("apron name")}\n
("conditional for" | "closed, except for" |  "prohibited for" | "allowed for")
(["aircraft"] ["flight"] ["PPR time" ["PPR details"]]) {["aircraft"] ["flight"]} ["PPR time" ["PPR details"]]} \n 
["reason"] "start time" "end time" [schedule] \n
[note].

...

Identifier

Data encoding rule

ER-01

The temporary limitation of an apron shall be encoded as:

  • a new Event with a 'BASELINE' TimeSlice (scenario='APN.LIM', version='2.0'), for which a PERMDELTA TimeSlice may also be provided; and
  • a 'TEMPDELTA' TimeSlice for each affected Apron feature, for which the "event:theEvent" property points to the Event instance created above;

ER-02

First, all the BASELINE availability.ApronAreaAvailability (with operationalStatus='NORMAL'), if present, shall be copied in the TEMPDELTA  (see Usage limitation and closure scenarios).

Then, an additional availability.ApronAreaAvailability element shall be included in each Apron 'TEMPDELTA' having:

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

If the apron 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-04

If the apron 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-05

If the apron 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-06If the apron 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-07

The "aircraft-flight-PPR" 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-08

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

ER-09

If the limitation concerns only 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 (with operationalStatus='LIMITED' or 'OTHER:EXTENDED') of all affected Apron TEMPDELTA Timeslice(s). See the rules for Event Schedules. 

ER-10

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

ER-11The AirportHeliport, where the Apron(s) concerned by the limitation is(are) situated shall also be coded as concernedAirportHeliport property in the Event.
ER-12If there exists aircraft stands on the Apron affected by the limitation and if the apron limitation makes the aircraft stand 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'. 

...