Code | Meaning |
ATL A D L | Traveler arrived at and departed from Atlanta, and had a layover there. |
LAX A D | Traveler arrived at and departed from Los Angeles. |
ORD L | Traveler had a layover at Chicago O'Hare, but no arrival or departure. |
An issue I found in my data is that I listed each flight separately in order, and the data only shows the final line with that airport in rather than stacking the multiple lines and saying that I've both landed and departed.Thanks for trying that. I had not considered that users might want to enter data that way, but will work on it some more and see if it's possible for the script to combine data from lines that begin with the same code.
This is perhaps more a feature request than a bug to fix.
I pulled in a couple of new .alist files on GitHub then pulled the results down onto the TM server. So the two new users are there now.
I couldn't force a hard enough reload in Firefox to see the updates, maybe I have to manually clear something from its cache. I'm seeing the latest data when I load in a different browser.
This point thing has potential for other uses - you could do a similar thing with other things that's basically a binary "I've been here" with some ability to give different codes to describe your visit. Eg National Parks (though preferably that would have areas that are coloured rather than points. But National Historic Sites would probably work better as points).
NAN is actually Nadi International in Fiji
Comments and suggestions welcome.Viewing by airport records all the lines in my file, unlike viewing by user.
Created a pull request for a new list. Let me know if I messed up: https://github.com/TravelMapping/AirportData/pull/23Got it, thanks. I tested it and everything looks great. The airport part of TM auto-updates at :15 past the hour, so check back then.
It might be useful to have a way to note that you visited an airport by a mode of travel other than airplane (e.g. if you were only there to pick up a passenger).