Versions Compared

Old Version 25

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.

...

Identifier

Data encoding rule

ER-01

The temporary change of an airport/heliport usage limitation shall be encoded as:

  • a new Event with a BASELINE TimeSlice (scenario=”AD.LIM”, version=”2.0”), for which a PERMDELTA TimeSlice may also be provided; and

  • a TimeSlice of type TEMPDELTA for the affected AirportHeliport feature, for which the "event:theEvent" property points to the Event instance created above.

ER-02

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

Then, an additional availability.AirportHeliportAvailability element shall be included in the AirportHeliport TEMPDELTA having:

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

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

ER-04

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

ER-05

If the airport/heliport is "prohibited for" specified operations, flight and/or aircraft categories, all specified limitations shall be encoded as AirportHeliportUsage child elements with type=FORBID.

ER-06If the airport/heliport is "allowed for" specified operations, flight and/or aircraft categories, all specified limitations shall be encoded as AirportHeliportUsage child elements with type=PERMIT.
ER-07

If a unique flight or aircraft is specified as part of the condition, they shall be encoded as one ConditionCombination with logicalOperator="NONE".

Otherwise, each pair of flight and aircraft shall be encoded as one ConditionCombination with logicalOperator="AND".

ER-08For every AirportHeliportUsage encoded, the aixm:operation shall be specified.

ER-09

The type of operations that do not match a pre-defined value in the FlightCharacteristics.status shall be encoded as follows:

  • emergency medical evacuation -> status=’OTHER:MEDEVAC’

  • fire fighting flights -> status=’OTHER:FIRE_FIGHTING’

ER-10

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

ER-11The AerodromeHeliport concerned by the closure shall also be coded as concernedAirportHeliport property shall be coded in the Event.

...