Open Airport Map
openairportmap.org
openairportmap.org
Very little airport surface data is made available in an open and machine-readable format (aerial navigation data is available openly in the US at least). Because of this only the big players (e.g., Boeing) have this data. OpenStreetMap users who contribute this data are democratizing access for anyone who wants to work with airport data in the same way global map data is democratized.
At the same time, data is only useful if you can make sense of it, and the first task towards being able to work with this data is visualizing it. A specialized mapping tool helps a lot here. Props to the author for making it!
One example use case: citizen scientists could develop and test new planning algorithms for airplane taxiing that are resistant to blockages and availability problems. This is science you could do right now only because data like this is available.
They might need combine/reduce the elements. Or use a canvas?
If you haven't done so, it's actually quite nice to skip the Plane Train and walk between the concourses; there's a very cool collection of Zimbabwean sculpture down there between the T and A gates.
https://community-cdn.openstreetmap.org/uploads/default/orig...
Ex: https://aeronav.faa.gov/d-tpp/2302/00568ad.pdf
Something like OpenStreetMap makes sense because there is no public domain published map of everything. I'm sure there is something obvious here I'm missing. Maybe it's just anything that isn't US might be the problem.
https://ww2.jeppesen.com/wp-content/uploads/2019/04/north-po...
You can use an app like Organic Maps (formerly Maps.me) or Osmand to access it.
They do have a locate button, but even clicking that didn't change the behavior.
One thing that has been suggested in this thread is that the map shows all airports -- this has been realized now.
I would love to hear your ideas how to improve the application. Let's improve it together. :-)
LUX and LCY are also interesting: comparable max passenger numbers of 4M-5M, LUX has 2x> as many weekend slots as LCY, presumably similar clientel (though LUX does more hub flights I reckon), and very different space and layout constraints.
It makes the life's of people like me who live near it much better! Even if it means that weekend flights from my nearest airport can be a pain
The reason I ask is that one of my local GA airports has constant pressure to reduce the movements from local residents, but the airport has been in frequent use since WWI so I can't understand why people move near an airport and then complain that there is an airport there.
LCY is a one-trick-pony: a private airport for European finance bros.
* Taxiway labels aren't very readable, and I need to zoom in quite a bit for them to even be consistently displayed.
* For that matter, the yellow lines seem to cover a lot of things that aren't taxiways, and seem to extend into non-movement areas (areas outside the purview of ground control/tower), and for that reason, they make the actual taxyways harder to see.
* The runways are labled in a way that requires consulting the compass rose to interpret - "10L/28R". "10L/28R" is the name for that strip of tarmac, but when you're landing with a heading of 284º, it's called "28R" and when you're landing the other way, it's called "10L". Compare that with the FAA diagram, which labels them clearly at the landing side of the runway, the same way the numbers are painted on the ground.
* The openairportmap diagram lacks runway length and width.
* OpenAirportMap lacks the location of the displaced thresholds on the 28 and 1 runways.
* OpenAirportMap lacks the location of the runaway airplane catchers (EMAS) at the ends of the 1/19 runways.
* OpenAirportMap lacks any field elevation information
* OpenAirportMap doesn't have an indication of north, or of the magnetic variance.
* SFO doesn't have a VOR on-field, but if it did, it's location would be printed on FAA map, but not openairport
* The FAA map has the ATIS (weather), Tower, Ground Control, and Approach Control frequencies listed on it.
Overall, I would say the openairport map is not useful to a pilot. Which I think goes to the GP's point: "what is the goal of this map?" It's not to help a pilot.
First, "this is not for pilots", it probably can be.
Second, the layout/design is not helpful, seems to be mostly nit picking (which is good).
Third, the data is wrong.
The data can be corrected on http://osm.org by anyone, so that means your first objection is true. The design and layout can of course be corrected over time, depending on how many people care about mapping/visualizing them. The question is can you land an airplane with this map, this will be tested in flight sims that will use the same data.
So I do not know the goal of this map, but I have entered data about airports in to Openstreetmap and I most certainly did not do it for pilots. This was ten years ago I see that the amount of data has grown incredibly, So there must be people that care about it. That makes me believe that all your objections will be solved. Except the first one I listed since we can't have an fully loaded passenger plane land based upon my data.
For instance, IFR charts (https://www.faa.gov/air_traffic/flight_info/aeronav/productc...) show just essential routing information.
Here’s an example taxi diagram: https://www.faa.gov/air_traffic/publications/atpubs/aip_html...
Again the key point I’m highlighting is lack of extraneous aesthetic.
The view is even more similar to that used by ATC: https://atctower.com/what-the-atc-controller-sees-tech-in-th...
If you’ve ridden a lot in planes, you may be used to looking at VFR sectionals (https://www.faa.gov/air_traffic/flight_info/aeronav/productc...). These have more aesthetic detail precisely because they’re intended for visual navigation.
Former Cartographer - deriding my paying attention you abandon yours.
Is Open Street Map intended for machines to digest and spit out in say a more readable manner?
Academics vs real life = such a wide distinction.
Thanks for the casual ad hominem. Interesting take that making practical data available for to anyone is a symptom of ivory tower delusion.
Ultimately, a person wrote a free and useful tool that can be used by anyone, and all you’ve done is deride it.
Pretty sure I clearly stated this looks nothing like the charts im used to. Further real world comments above explain why this map is to put politely, lacking.
Major major difference between maps and data. Perhaps sitting in on Geog 120 or whatever it is wherever you are, would be wise. Hop in a seat of a Cessna 150 would too.
Edit: it does appear that hold lines are mis-tagged in some spots, e.g. north of arrival end 25C.
Addendum: someone mentioned Airnav. Just to see the lack of open and up to date data available freely, look at SFO [1] and look at YYZ [2]. SFO has an airport diagram showing taxy ways and runways and some other meta information. nothing for YYZ.
"remark": "runtime error: Query timed out in \"query\" at line 6 after 29 seconds."
I say bogus error message because for sure that URL did not take 29 seconds to return (221ms according to Firefox). I'd guess the query is malformed and their api interprets the error as a "timeout" instead of "error"But.. looking for "London", 2 of the first 3 airports are in North America and arguably a lot of people would not count any of the first 5 (Lydd, Oxford & Southend) as London. Heathrow doesn't show up at all without specifying further.
In theory, they could build a system which returns relevant airports ranked by size in terms of latest/peak passenger traffic figures
Tags:
addr:city=Denpasar
aeroway=aerodrome
iata=DPS
icao=WADD
name=Bandar Udara Internasional Ngurah Rai
name:de=Internationaler Flughafen Ngurah Rai
name:en=Ngurah Rai International Airport
name:fr=Aéroport International Ngurah Rai
name:ko=응우라라이공항
operator=PT. Angkasa Pura I
short_name=Bandara Internasional Ngurah Rai
type=civil
wikidata=Q1061846
wikipedia=id:Bandar Udara Internasional Ngurah Rai
Colloquial names can be added with the various name tags:
https://wiki.openstreetmap.org/wiki/Names#Local_names_(loc_n...
(I'm assuming the search is sourcing data from OSM).or London Heathrow to Oxford Airport in around 60mins
that's no time at all compared to the driving distances between major US cities, which I'm guessing is what this is based on
Looks like the site was setup by a german (or at least someone that lives in Germany and speaks german).
It supports searching for other parts of the name (or closest (big-ish) city that airports tend to name themselves after).
However, the search seems to not work with spaces, so can only search for one word in the name, it seems.
I don't think being built by a German speaker has anything to do with it. Typing "Vienna" (the English name for the city) returns the expected airport first, perhaps because the IATA code is VIE. Typing "Wien" (the actual name of the city in German, used by the locals) puts it further down the list among funny little airfields in other places.
The UX lesson for us all: sorting of search results is hard. It helps to know who your users are, and what they are looking for. Fundamentally, my bigger question with this site - which looks awesome, and is fun to geek out over - is who is it for? Professional pilots obviously have their own resources already to tell them how to navigate around airports, where to park and where to taxi; the detailed information that would actually be useful for a first-time passenger at Frankfurt airport is completely lacking, eg. how long will it take me to transfer from an inbound London flight to my connection to a small town in Austria, how can I find shortcuts to shave a few minutes off that, will I have to go through extra security checks (the answer varies with the direction of travel and, apparently, the time of day), is it more convenient to stop off in the business lounge of the terminal where I arrive, before transferring, or the one that might be close to my departure gate, can I still enter Schengen through the electronic gates with a UK passport or must I join a long queue with the Americans and Japanese, where can I refill my water bottle and charge my phone for free, etc etc etc
The UX lesson here is that geocoding names to coordinates is hard. It's always a bit subjective. Another lesson is that search ranking is hard. Even though this is fine, it could be improved a little:
- take into account distance
- take into account size of the airport (number of graphical elements, runway, surface area, etc.)
- take into account size of nearby cities (there is some open data for that)
- support fuzzy search
- etc.
Also the whole asking for location unprompted, and not respecting a refusal... dumb.