Closed 16-9 closed 8 months ago
Hi! When I tested - estimated times were undefined, but scheduled times were defined and correct. Maybe better to use scheduled times ?
I am not too sure at which point FR24 documents those fields. I have indeed seen flights where estimated is null. Fetching https://data-live.flightradar24.com/clickhandler/?version=1.5&flight=33a498e0 for a flight that is about to shortly land in SFO provided me: ... "time": { "scheduled": { "departure": 1705426800, "arrival": 1705433280 }, "real": { "departure": 1705428107, "arrival": null }, "estimated": { "departure": null, "arrival": 1705432303 }, "other": { "eta": 1705432303, "updated": 1705428711 }, "historical": { "flighttime": "4660", "delay": "-934" } },
We could have scheduled, real, and estimated whether there is a value or not.
Ultimately, what would be great would be to have the ability (a service maybe) to create a device_tracker for a flight given its callsign or flight number independently of a tracking zone.
Added
@16-9 Dont forget please to give a star to the repo :)
Alexander,
Would you consider exposing the estimated departure and arrival times of a flight as well? That information is made available by Flightradar24 as well. It would allow me to track a plane's arrival and inform me when it is time for me to leave to pick someone up at the airport.
Thanks,
Christophe