Isn't there some kind of associated database which would classify each road according to importance or rank? A simple filter on that data field should do the trick. But then I don't really know anything about the OSM data format. But certainly, if you could find a way to use these data you'd be home safe.

-- Chris.

I'm a bit surprised by this answer. SkyDemon is marketed as a VFR tool. In VFR flying, pilotage is the primary means of navigation. Radio navigation, including GPS, is a great help but can and should not be used as the sole means of navigation.

at least concerning the restriction area LO-R 18 east ofst gallen/altenrhein (LSZR) not. the eastern boundary is more or less thewestern shore of the river rhine (legally it's a lot more complex, i know).

almost all german forums criticize not the aviation dataitself but the ground data as skydemon is viewed as a means of getting rid ofpaper charts, esp since jeppesen no longer publishes vfr-gps charts. it'smarketed this way.

i also strongly urge to get a better data source or givea statement concerning each area/state. this is definitely seen a problematictopic in this part of the market.

otherwise keep going, well done product!

harald

Today we published new charts for Austria, Switzerland and the surrounding area (but mainly those two) with very much improved spacial accuracy of roads, railways, rivers etc.

Wow, the new charts are very detailed. But it seems there is some "old data" left, for example in LOWG there are two parallel highways tomthe south, which is wrong - just one is there in real. Didn't search for other errors yet, maybe some others can check these charts too and report any mistakes here.

Cheers,
Bernhard.

Hopefully this issue around the borders of the affected areas should resolve itself in the next AIRAC update. It's only because we published an interim chart update that some of the unfixed data is still present. We will take a look at it.

Hi Tim,

regarding OSM background data: I, too, had the problem in a project with my company, that we wanted to retrieve vector maps (to our own proprietary format) from OSM but found them to be often too detailed.
In the end, I set up some GIS server and run customized queries which also did some simplifications to reduce too complex polygons, lines, etc. (like removing too many verticies, removing very small lakes, forests, ...)
On the other hand, esp. roads are still very accurate at our required zoom levels.
PM me, if you are interested in more details.

Cheers,
Markus

Naïve detail reduction on polygons and polylines cannot be used on OSM road data to make it useful. We already use such algorithms on the data we have. The biggest problem with using OSM data is that roads with a median are represented as more than one polyline, and merging these is a very nontrivial task. Also, we found the railway data to be very unreliable. Thanks for the offer though.