Each project may define a list of events which if they arise will trigger an email notification.
The list of supported events and their description:
takeoff_from_airport
This event is triggered when a takeoff first begins, and the origin airport was successfully
determined. This signal comes from the aircrafts State.IsOnGround field changes from true
to false. Internally, this sets the IsInTakeoff SightingTag.
Note this event requires the track_takeoff feature to be enabled.
takeoff_unknown_airport
This event is triggered when a takeoff first begins, but we failed to determine the nearest airport.
The trigger and behaviour is the same as takeoff_from_airport.
Note this event requires the track_takeoff feature to be enabled.
Note if no airport location files are configured, the only emitted will be takeoff_unknown_airport.
takeoff_complete
This event is triggered when a takeoff is complete. This event can only be produced if the takeoff_from_airport
or takeoff_unknown_airport trigger was encountered, as it relies on the IsInTakeoff SightingTag.
The actual signal comes from the vertical rate finally being set to zero, if and only if the
IsInTakeoff SightingTag is true.
Note this event requires the track_takeoff feature to be enabled.
spotted_in_flight
This event gets triggered when an aircraft sighting is first opened.
map_produced
This event gets triggered when an aircraft sighting closes, if a KML was produced.
Note this event requires the track_kml feature to be enabled.