Definition

The notification about the temporary existence of a wildlife hazard at an airport.

Notes:

  • this scenario shall be used to notify that wildlife hazard is present at an airport. 

  • this scenario does not include a permanent change in the duties, means and procedures of the aerodrome that are related to wildlife hazard mitigation. These are usually included in the aerodrome manual and stakeholders' procedures manual. 
  • No NOTAM - this is a scenario for which it is unlikely that a NOTAM would be ever issued. The digitally coded data only might be made available to the interested parties through a digital data service at the airport level.

Event data

The following diagram identifies the information items that are usually provided by a data originator for this kind of event. 

EBNF Code 
input = "designator" ["name"] \n
"description of wildlife hazard" "start time" "end time".

The following table 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

designator

The published designator of the airport/heliport concerned. This information, in combination with eventually the name is used to identify the airport/heliport.

AirportHeliport.designator

name

The published name of the airport/heliport. This information, in combination with the designator is used to identify the airport/heliport.

AirportHeliport.name

description of wildlife hazard

The description of the wildlife hazard to be notified

AirportHeliport.annotation with purpose=OTHER:WILDLIFE_HAZARD

start time

The effective date & time when the wildlife hazard is identified and reported.

Airport/AirportTimeSlice/TimePeriod.beginPosition, Event/EventTimeSlice.validTime/beginPosition and Event/EventTimeSlice.featureLifetime/beginPosition

end timeThe effective date & time when the wildlife hazard is expected to cease. Airport/AirportTimeSlice/TimePeriod.endPosition, Event/EventTimeSlice.validTime/endPosition and Event/EventTimeSlice.featureLifetime/endPosition

Assumptions for baseline data

It is assumed that information about the aerodrome already exists in the form of AirportHeliport BASELINE TimeSlice(s) covering the complete period of validity of the event, for which the baseline availability is coded as specified in the Coding Guidelines for the (ICAO) AIP Data Set.

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. To the maximum possible extent, the compliance with these encoding rules shall be verified with automatic data validation rules.

Identifier

Data encoding rule

ER-01

The notification about the temporary existence of a wildlife hazard at an airport shall be encoded as:

  • a new Event with a BASELINE TimeSlice (encoding=”DIGITAL”, scenario=”WLD.HZD”, 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

The description of the temporary wildlife hazard shall be encoded in the AirportHeliport TEMPDELTA in an annotation with purpose=OTHER:WILDLIFE_HAZARD. 

ER-03

The gml:endPosition shall have indeterminatePosition="unknown". 

Rationale: As the LVPs are weather dependent, an endPosition cannot be specified. 

ER-04

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

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

Examples

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



  • No labels