We would like to use the historical data for flights, but comparing it with the ‘/flights/{ident}’ the history path is not returning inbound_fa_flight_id.
One example:
ident = CV6694
Flight we need is GDL to LUX, but this consists of two flights (GDL-IAH, IAH-LUX). The two flights can be linked using the inbound_fa_flight_id.
Could you please check why on ‘history’ path we don’t get this value populated? It works on the normal path /flights/{ident].
You can simply test with current dates, these flights happen quite often.
Tested with:
start = 2023-09-18
end = 2023-09-22
/history/flight/{ident} - returns null values for this element
/flight/{ident} - returns the value correctly
We state in the documentation it does not populate.
The field inbound_fa_flight_id will not be populated by this resource.
https://www.flightaware.com/aeroapi/portal/#get-/history/flights/-ident-
Taylor Fischer -
Commercial Support
Toll Free: +1.800.713.8570
Support Line:+1.713.588.6514
Eleven Greenway Plaza, Suite 2900 - Houston, Texas - 77046
–
Learn about FlightAware Global and Premium Accounts: http://flightaware.com/commercial/
Is there any reason why? You have the info in the live data, so what is the problem in keeping it for the historical data.
This way you are limiting the usage of historical data, quite a bit.
Unfortunately it is a technical limitation at the moment. The inbound_fa_flight_id field is determined dynamically when it is requested and it is a somewhat time-intensive query to scan for the possible connecting flights. It’s not too bad of a query for the recent flights (last 14 days), but on the historical tables it cannot currently be executed in a reasonable amount of time due to the different database indexes on our historical warehouse system.
