[mkgmap-dev] default style: highway=path means unpaved?

Tue Sep 8 09:32:14 BST 2015

Well that was introduced because it is unknown. If you have a map and want
to avoid unpaved ways - and select that - then there really should be no
unpaved ways. If we don't set unpaved here - the avoidance will not be
strict enough anymore...
highway=path & bicycle=designated could well be a tracktype=grade2 and
sometimes even grade3 or worse... And in cases of a mtb route - clearly
something completely unrideable for a normal cyclist...

On 8 September 2015 at 10:19, Gerd Petermann <
gpetermann_muenchen at hotmail.com> 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 at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>

-- 
Felix Hartman - Openmtbmap.org & VeloMap.org
Floragasse 9/11
1040 Wien
Austria - Österreich
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20150908/f67a4c33/attachment.html>