Closed maidough closed 2 weeks ago
oops, that was a mistake. fixed
Thanks, missed that too!
Added that to the github actions, it will now automatically check it on every PR.
Just want to chime in here @mwgg :
IMO, while not correct, I like the idea of prefixing it with a 'K'. However, we must certainly address this from a consistency perspective because right now we do both...
The key should match whatever is in the icao
field. Many years ago, when it was a MySQL table in a project of mine, that's how it was exported for this repo, and that's what it says in the README. Obviously it's not always ICAO, sometimes it's the FAA identifier.
I do see that we have FAA identifiers both ways. About 200 entries with the 3-letter identifier and way more with the K prefix. For the sake of consistency I agree that we should have it the same way, and the K prefix is a common way of denoting FAA identifiers.
I've changed the existing 3-letter entries, and added a check to be performed on each PR to ensure it's always 4, as well as verifying the key matches the icao field.
I noticed that the latitude and longitude for the new airports are strings which doesn't follow the convention in the rest of the file. Thanks for all the additions!