Page Comparison

Introduction

The lifetime of an Event is dictated by both its genuine duration and its intended use as notification mechanism. The Event needs to remain valid as long as it might need to be selected for entry in a pre-flight information bulletin.

• in the case of a temporary situation, the Event will have a lifetime equal to the time extent of the situation.
• in the case of a permanent change, the Event will have a lifetime that starts with the effective date/time of the change and ends when the changed information is integrated in the reference AIS digital data set (such as the AIP data set) or pre-formatted product (such as the AIP).

It shall be noted that the Event is a regular AIXM feature, therefore it has TimeSlices. This allows updating an Event:

• each Event will be first encoded as a BASELINE TimeSlice, for which a PERMDELTA may also be provided;

• an eventual change in the Event information (the equivalent of a NOTAM Replacement or Cancellation) can be encoded with additional Event TimeSlice, applying the same Temporality rules as for any other feature.

  Warning
  title ToDo
  Wolfgang Scheucher Sep 25, 2019 Could examples be provided for NOTAM C and NOTAM R scenarios. What values will the Event validTime and featureLifetime get? François Germain 4:39 PM Apr 29 Comment above to be dealt with consistently with comments in confluence here: https://ext.eurocontrol.int/aixm_confluence/display/CGWIP/Event+in+force+%28active+or+inactive%29+-+end+time+update

No use case has been identified for temporarily updating an Event with a TEMPDELTA Timeslice, therefore TEMPDELTA Timeslices are not expected to be used for Event.

Most events will need a single feature TimeSlice to be provided. For example, the activation of a temporary restricted area will require a single Airspace TimeSlice of type TEMPDELTA. However, there might exist events that require several TimeSlices to be encoded in several different features. For example, the establishment of a new obstacle (temporary or permanent) requires two AIXM features to be encoded or modified:

• first, a new VerticalStructure needs to be encoded;
• second, associations between the affected ObstacleArea(s) and the new VerticalStructure might need to be established.