TM Airports

[vdeane]

Highway interchanges seems like a useful one, especially since there have been multiple AARF threads on the subject.

I agree that this is the most logical 'next thing' to have a similar treatment to airports, though bejacob's point about going slow is a good one.

This one has the potential to fit better within the main TM highways code base.  Without thinking too much about how hard it would be, I imagine list files entries that could be expanded to allow a list of all waypoints where the user has entered or exited a route, have this information displayed with different icons on Mapview and Showroute, and various stats and rankings could be provided.

And I agree with the overall comment that there should not be a rush to expand to all of these other ideas.  An overall approach similar to what TM did in expansion to railways, where there's a common code base that ingests different sets of data, seems it would make sense. 

Eh, trying to put something together like that as a .list file for all points (and not just interchanges) is more work than I'd want to do for my travels.  If it were done that way I'd probably just ignore it and hope that the way it's implemented would only show up if the user engaged with it.

[mapcat]

The process of adding new airports is now automated, so all airports should be visible any time your map is created or updated.

We're over 500 airports now, including several military airports added today.

[oscar]

We're over 500 airports now, including several military airports added today.

The ones I noticed on the updated airports list all have IATA codes. I was toying with the idea of claiming at least two airstrips, where planes use specially-widened and straightened parts of the Dempster Highway in the Yukon (YT 5) and the Northwest Territories (NT 8 ). One, in Eagle Plains YT, has a sign warning highway travelers not to stop on the airstrip. Alas, they have no IATA codes or scheduled passenger flights, so the military airports are probably not a good enough excuse to add those airstrips.

[SSOWorld]

Looking back at my stats, I did it differently than what you have.  Since I have departed and arrived to every airport (I did "origin", "destination" and "connection" (which matched your "Layover").  How I flew required me to arrive and depart from every airport (via round trip) except two - GTF (dep only) and BIL (arr only) - which proves the use of the arrival/departure ticks. Could there be some form of "origin"/"destination" method either in parallel with (preferred) or replacing.  The parallel method would do well to allow for the multi-city methods (like a round-the-world trip). I considered making HNL a "Layover" but that depends on one's definition - I built my own connection (booking with Delta and Hawaiian directly)

[mapcat]

Looking back at my stats, I did it differently than what you have.  Since I have departed and arrived to every airport (I did "origin", "destination" and "connection" (which matched your "Layover").  How I flew required me to arrive and depart from every airport (via round trip) except two - GTF (dep only) and BIL (arr only) - which proves the use of the arrival/departure ticks. Could there be some form of "origin"/"destination" method either in parallel with (preferred) or replacing.  The parallel method would do well to allow for the multi-city methods (like a round-the-world trip). I considered making HNL a "Layover" but that depends on one's definition - I built my own connection (booking with Delta and Hawaiian directly)

It seems that you're talking about something similar to si404's .alist. It's probably doable, so I will try to make some time tomorrow or Saturday to finally work on this. If you want to submit another .alist with your preferred format (under a different name) that would be useful for testing.

[SSOWorld]

added "ssoworld1.alist". I put comments indicating what I'm interpreting. D = origin, A = Destination - Layover the same

https://github.com/TravelMapping/AirportData/pull/51

The change of ssoworld.alist was due to a botched cherry pick that I had to recover.  you won't notice it

[mapcat]

Users can now generate maps and tables with more than one .alist format. The standard format still works, but now airport codes can appear on different lines if the user chooses, allowing users to order airport visits by individual trip.

Example: this is the standard format for a user who traveled from PDX to DFW round trip:

PDX A D
DFW A D

However, using the new format will produce the same results:

PDX D
DFW A
DFW D
PDX A

In the past, the script rewrote the data for an airport every time it was encountered.

Thanks to si404 for suggesting this. Other suggestions are welcome.

[jayhawkco]

Just added mine. I used L for visits where I didn't leave the airport, despite having obviously arrived and departed.

[jayhawkco]

It doesn't look like the airport adding automation is working.

Edit: Just took a little while. Went from 106 to 179 airports. It appears I'm still missing 1H2 (Effingham, IL) and FRU (Bishkek, Kyrgyzstan) however. Maybe more that I just haven't found yet.

[oscar]

It appears I'm still missing 1H2 (Effingham, IL) and FRU (Bishkek, Kyrgyzstan) however. Maybe more that I just haven't found yet.

Bishkek's international airport's IATA code is now BSZ.

Effingham's airport appears not to have an IATA code. That seems a requirement for TM Airports to map an airport, and screens out some of the rural airstrips I had considered adding to my list.

[jayhawkco]

It appears I'm still missing 1H2 (Effingham, IL) and FRU (Bishkek, Kyrgyzstan) however. Maybe more that I just haven't found yet.

Bishkek's international airport's IATA code is now BSZ.

Effingham's airport appears not to have an IATA code. That seems a requirement for TM Airports to map an airport, and screens out some of the rural airstrips I had considered adding to my list.

Gotcha. Thanks for that. I'll edit my list.