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.
* 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.
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.