The problem is that it works too well. Paved roads with some potholes which are marked as bad are avoided. On the forum there is support for skipping smoothness=bad from the list of unpaved options, but to add a road_speed penalty instead. I think of adding this rule after the unpaved rules highway=* & mkgmap:unpaved=0 & smoothness ~ '.*(bad|horrible|impassable)' { add mkgmap:road-speed = '-2' } ________________________________ Van: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> namens Gerd Petermann <GPetermann_muenchen@hotmail.com> Verzonden: maandag 30 januari 2017 03:10:15 Aan: Development list for mkgmap Onderwerp: Re: [mkgmap-dev] Is smoothness=bad unpaved? I did not try if the rule itself works. If it catches "bad", "very_bad", and all worser values I think it is good as it is. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von lig fietser <ligfietser@hotmail.com> Gesendet: Montag, 30. Januar 2017 10:07:07 An: mkgmap-dev Betreff: [mkgmap-dev] Is smoothness=bad unpaved? Hi list, On the Garmin OSM forum there is a discussion started whether we should consider smoothness=bad as unpaved. In the default rules it is treated as unpaved. What do you think? Should we adapt the rules and skip 'bad' from the unpaved list? https://forum.openstreetmap.org/viewtopic.php?pid=628555#p628555 _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev