It’d be nice if there was a flag we could provide in our query to FXML3’s AirportBoards that would include flights that previous queries for an airport would have picked up, but have since gone away, for cases where the plans just drop out of the system, the unconfirmed arrivals (as mentioned at top of this post), flights that divert to another airport, etc.
For example, if a flight plan drops out of the system, add ability to keep it in the results but set the status indicator to dropped. If a flight diverts to another airport, keep it in the results set, but indicate it’s diverted… otherwise we need to do additional queries on flights that have stale data, and pinging each one against the API can get pretty expensive, especially if monitoring a large number of airports - it’s an impractical solution.
Also - not sure if it’s supported by data, but I’ve been noticing more duplicate flights lately, where AirportBoards or push alerts are coming through with different FA flight IDs for the same flights - it’d be cool if there was an added field you could include when/if your system catches the flights as duplicates that would just be a set of FA flight IDs for other flights that ended up being the same. I can do a fair amount of duplicate detection on my end, but, it’d be nice if there was so help coming from your end too.