Take-off place and time zone
| Platform | Status | Where |
|---|---|---|
| iOS | done | vulture-ios/Packages/Flights/Sources/Flights/Enricher/FlightTakeoffEnricher.swiftvulture-ios/Packages/Airportsvulture-ios/Packages/Flights/Sources/Flights/Vendor |
| Android | done | vulture-android/data/dbvulture-android/domain/flightvulture-android/domain/airportsFlights imported on Android before the take-off airfield port (2026-10-20) keep no airfield. |
Behaviour
Section titled “Behaviour”- The take-off airfield and its country are looked up in the bundled airports data (OurAirports) and shown in the list and the detail.
- The take-off country feeds the countries filter of the logbook.
- The local time zone of the take-off comes from a bundled
timezones.json, so times are shown in local time.
Platform differences
Section titled “Platform differences”- Android bundles the same
airports.json(domain/airports) and looks up the take-off airfield on a flight’s first analysis only, so flights imported on Android before the table was ported keep none, also after a re-analysis; iOS looks it up wheneverisTakeoffProcessedisfalse. Built on main, not released yet (Take-off airfield on Android). The airport screens stay iOS-only. - The time zone lookup is ported to Android (golden fixtures include time zones).