ntilley905 / faadelays Goto Github PK

While doing some work on implementing a new feature, I noticed that while the API explicitly refers to the returned IATA code as IATA, it appears to actually be returning the FAA code. An example can be seen with State College, PA which has UNV FAA code vs SCE IATA code. If you call the API using SCE it does not recognize the airport. If you call it with UNV, you receive the correct State College data with UNV returned as the IATA code. I've reached out to the API contact email address for clarification.

FWIW, this is outside of the "supported" functionality of the API, as State College is not listed as a supported airport. I do think that all of the supported airports have matching FAA and IATA codes, and so this may be a known (and not intended to be fixed) issue. If so I'll have to update documentation to resolve the discrepancy. While the FAA only supports data within the supported airports list, my aim is to support all airports for which the API returns data.

The FAA has shutdown the old API and moved to a new endpoint. The new API presents the data in a different format so the changeover will be more substantial than a simple URL change.

Follow this issue for progress!

Need to write some tests for the code base so that I don't need to wait for live data before merging new changes.