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] "status=CLOSED" ["closure reason"]\n
"start time" "end time" [schedule] \n
[note].

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
status=CLOSED	The operational status of the airport. In this scenarios, it is only possible to indicate a complete closure.	AirportHeliport/AirportHeliportAvailability.operationalStatus
closure reason	The reason for the airport/heliport closure.	AirportHeliport/AirportHeliportAvailability.annotation with propertyName="operationalStatus" and purpose="REMARK". Note that the property "warning" of the AirportHeliportAvailability class is not used here because it represents a reason for caution when allowed to operate at the airport, not a reason for a closure.
start time	The effective date & time when the airport closure starts. This might be further detailed in a "schedule".	Airport/AirportTimeSlice/TimePeriod.beginPosition, Event/EventTimeSlice.validTime/timePosition and Event/EventTimeSlice.featureLifetime/beginPosition
end time	The end date & time when the airport closure ends.	Airport/AirportTimeSlice/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 airport/heliport is effectively closed according to a regular timetable, within the overall closure period.	AirportHeliport/AirportHeliportAvailability/Timesheet/... according to the rules for Schedules
note	A free text note that provides further details concerning the airport closure.	AirportHeliport/AirportHeliportAvailability.annotation with purpose='REMARK'

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 may be 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 temporary closure of an airport/heliport shall be encoded as: a new Event with a BASELINE TimeSlice (scenario=”AD.CLS”, 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 AirportHeliport.availability.AirportHeliportAvailability (with operationalStatus='NORMAL'), if present, shall be copied in the TEMPDELTA (see Usage limitation and closure scenarios). Then, an additional AirportHeliport.availability.AirportHeliportAvailability element having operationalStatus='CLOSED' shall be coded in the AirportHeliport TEMPDELTA.
ER-03	If the airport 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 AirportHeliportAvailability having operationalStatus='CLOSED'.
ER-04	The system shall automatically identify the FIR where the AirportHeliport is located. This shall be coded as corresponding concernedAirspace property in the Event
ER-05	The 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):

DN_AD.CLS_with_daily_schedule_on_baseline_with_schedule.xml

Browser not supported