docs(wiki): live flight status and FLIGHT_LIVE_ENABLED

The transport page explains what TREK follows, where it shows and what open
data cannot give; the environment page documents the switch and what leaves
the server.
This commit is contained in:
Maurice
2026-11-13 15:36:43 +01:00
parent 41134cc455
commit 2d95bf6744
2 changed files with 24 additions and 0 deletions
+12
View File
@@ -365,6 +365,18 @@ When left at the default, using the transit feature makes the TREK **server** se
---
## Live Flight Status
Booked flights are followed live through the keyless open ADS-B networks adsb.lol and, on a self-hosted install, adsb.fi. See [Transport: Flights, Trains, Cars](Transport-Flights-Trains-Cars#live-flight-status).
| Variable | Description | Default |
|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|
| `FLIGHT_LIVE_ENABLED` | `false` switches live flight status off, `true` keeps it on; either way it wins over **Admin → Settings → Live flight status**, which then shows the value locked. Unset leaves the choice to the admin switch. | unset |
While on, the TREK **server** asks `api.adsb.lol` (and `opendata.adsb.fi` on a self-hosted install) for the callsign of each booked flight in its watch window, at most once a second and 200 times an hour. Nothing else about the trip or its travellers is sent.
---
## Image Search (Unsplash)
TREK can search [Unsplash](https://unsplash.com/) for **trip cover images** and **place images**. By default the server queries Unsplash's public web endpoint **without an API key**, so no configuration is needed on most installs.
+12
View File
@@ -132,6 +132,18 @@ For a transport, the tiles at the top show the departure and arrival times with
From the plan, **Edit** on a transport needs the right to edit days; on the Transports tab it needs the right to edit bookings.
## Live flight status
TREK follows every booked flight on its day, with no API key and at no cost: the server asks the open ADS-B networks [adsb.lol](https://www.adsb.lol/) (and [adsb.fi](https://adsb.fi/) on a self-hosted install) where the aircraft flying the booked flight number is, from three hours before departure until two hours after arrival.
- **The booking detail** on the desktop and the transport sheet on the phone show a boarding pass: what is happening now ("Departs in 2 h 10 min", "In the air", "Landed"), both airports with the planned and the expected or actual times, the route as an arc with the aircraft on it, and altitude, speed, remaining distance and aircraft while it flies.
- **Booking cards and the day plan** say the same in one line, with a progress bar while the flight is in the air and the delay beside it.
- **The trip map** draws the aircraft at its live position, turned to its heading; click it to open the booking.
- **Notifications** report take-off, landing and a departure 15 minutes or more late, to the booking's travellers (or the whole trip), each once. Each traveller picks the channels under Settings → Notifications.
- **The apps** have a Flight widget and turn the travel day's Live Activity into a boarding pass around a flight.
Delays and the arrival estimate are worked out from the aircraft's positions. Gate, terminal and baggage belt are not part of open data; add them to the booking if you need them. A flight whose airline flies under another callsign, or a codeshare, may not be found: the booking then says "No live data". Only the flight's callsign leaves the server. An admin can switch the feature off under **Admin → Settings → Live flight status**, or with `FLIGHT_LIVE_ENABLED` (see [Environment-Variables](Environment-Variables#live-flight-status)).
## On the map
A transport with both ends set can be drawn as a line on the trip map: