Open moshobo opened 4 weeks ago
Thanks for making me aware of this problem.
Your suggestion is a valid one. I think the way i'll be fixing this is, as you suggest, is to prioritize the gps_code
column whenever it is present over the ident
column. I might just discard the ident
ICAO in those cases, but I'll look into any issues that this could create.
There are a few airports that have updated their ICAO airport code, but JetLog doesn't show the updated version. In my case, I have flights to Kenneth Kaunda International Airport in Lusaka, Zambia. The current ICAO code is
FLKK
, but jetlog currently usesFLLS
.I took a look at the airports database source and when viewing the raw csv file, it appears that the old ICAO code
FLLS
is theident
value for this airport. However, thegps_code
value isFLKK
, the new ICAO code. I assume this is the case so that there aren't any duplicate entry rows as existing airports are renamed. Instead the new ICAO code just gets put ingps_code
.I propose that if a
gps_code
exists the UI should use it instead of theident
(aka the old ICAO code). It appears that this is how OurAirports seems to handle it too. Here's the example for the airport in my example; notice how the URL isFLLS
but the page text shows the newFLKK
(example link). Implementation wise, I'm not sure if its best to change the existingicao
to be similar to OurAirport'sident
, or just add a newgps_code
variable to theAirportModel
Class.