
Hi all, I think I should add that in Germany we have thousands of these ways, and I am very sure that most of them are paved. The reason is that Germany is full of signs like 237 , 241, and 242 (see http://osmtools.de/traffic_signs/) and that page still recommends to use the tags "highway=path" and "bicycle=designated" for them. In Germany a cyclist has to use these ways, so you can be pretty sure that they are paved. So, maybe we can add an exception for Germany? Gerd GerdP wrote
Hi all,
I just noted that the default style sets the mkgmap:unpaved flag for many cycleways, e.g. http://www.openstreetmap.org/way/276070019
I see intensive discussions about wrong use of highway=path and/or wrong interpretation of that tag.
The rule in lines is (highway=bridleway | highway=path | highway=track | highway=unsurfaced) & surface!=* & tracktype!=* & smoothness!=* & sac_scale!=* { add mkgmap:unpaved=1 }
My understanding is that highway=track is likely to be unpaved, but highway=path doesn't suggest that, esp. not in combination with bicycle=designated.
Does anybody have a better solution?
Gerd
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/default-style-highway-path-means-unpaved-tp58... Sent from the Mkgmap Development mailing list archive at Nabble.com.