Please read: This is a community-maintained wiki post containing the most important information from this thread. You may edit the Wiki once you have been on FT for 90 days and have made 90 posts.
Temporary wiki. Please read before changing: thanks! usAir created this wiki to hold the entire contents of the Airline Route Mapper data file. I've just edited it to remove that data, so should explain why: I appreciate usAir's initiative, but don't think the wiki in that form was a step forward.
1.) The data file is IMO too large to post in this location. Some (if not all) browsers load the entire wiki each time the thread is accessed. That had the effect of killing my browser for two to three minutes, then slowing my computer dramatically (and my setup, while not especially good, isn't the world's worst: DSL connection, latest Firefox version, 8GB RAM).
2.) The data initially posted were old ("from the last version of the airline route mapper", according to usAir's post on March 9 2015) and easily accessible (download Link: http://arm.64hosts.com/AirlineRouteMapper.zip), so nothing is lost by removing them from the wiki.
I've also wanted this kind of a tool for a long time. I really like ITA Software's "graphical" bar chart view of flight/layover options and I think this mapping tool is the major missing view of the data that ITA displays.
congratulations and thanks - cockpitvisit,
this is a great application and it is a joy to use it.
however - would it be possible to make the application in a way that the user could also just choose an airport and would get all the destinations served from there (irrespective of the airline)?
however - would it be possible to make the application in a way that the user could also just choose an airport and would get all the destinations served from there (irrespective of the airline)?
If you select All airlines and then click on an airport, it will show all routes starting at that airport and the corresponding destinations. You may want to disable the display of routes to avoid clogging the window with other routes.
If you select All airlines and then click on an airport, it will show all routes starting at that airport and the corresponding destinations. You may want to disable the display of routes to avoid clogging the window with other routes.
Exactly what I was looking for. Thanks again
Robert
Programs: OZ*G, QF QPPS, VA gold, NZ*roach, Former 'bottom-feeder' AC*G, AB gold, DL plat
Posts: 4,765
This app rocks! Thank you, cockpitvisit. Quite apart from the useful side of it (finding out who flies to given airports etc) it's absolutely great for satisfying my idle curiosity, like for example being able to see the entire Star Alliance route network at once, or seeing what the real route maps look like for some big airlines that don't publish them. Nice!!
Airport MWX is shown to be East of Cuba instead of being in Korea.
Thanks, will be corrected in the next update!
Quote:
Anybody know of a similar capability, in an application or website, for us Mac owners?
No idea, but I had reports of Mac users being able to run it under VMWare.
The data files are included in plain text format, so if anyone is willing to build a Mac app or a website, they are welcome
This is indeed a wonderful tool!
I'm using it to find a route for Global Explorer RTW trip.
In addition to oneworld airlines, it allows flights on all these:
AA AY BA CX EI FJ GF IB JC JL JO KA LA LP MA MX NU QA QF RJ XL 4M
Plus all QF codeshares on 6 different airlines.
The problems I have:
1. QA is not in database of your tool.
2. If I allow codeshares, then ALL codeshares of these airlines pop-up, while I am interested only in QF codeshares, and to limit even more only the QF codeshares on the 6 airlines that are allowed.
I presume that this could be quite popular search patter, so could you help me how to search for these flights? At the moment I use custom pattern with AA AY BA CX EI FJ GF IB JC JL JO KA LA LP MA MX NU QA QF RJ XL 4M.
usAir created this wiki to hold the entire contents of the Airline Route Mapper data file. I've just edited it to remove that data, so should explain why: I appreciate usAir's initiative, but don't think the wiki in that form was a step forward.
