Another issue that is related to the unpaved rules is posted by Peter 'Beddhist' on the forum:

https://forum.openstreetmap.org/viewtopic.php?pid=630231#p630231

highway=track & surface=paved is marked as unpaved by mkgmap.

This isssue is caused by this rule:

(highway=bridleway | highway=path | highway=track | highway=unsurfaced)
& surface!=* & tracktype!=* & smoothness!=* & sac_scale!=*
{ add mkgmap:unpaved=1 }

If my interpretation is correct, it says that all those types of highway are considered as unpaved, unless there is a surface, tracktype, smoothness AND sac_scale parameter!


I think  it should add mkgmap:unpaved=1 unless

- surface=paved,asphalt,concrete, etc* OR

- tracktype=grade1

- smoothness and sac_scale?


*) surface values that are paved are mentioned in the wiki: http://wiki.openstreetmap.org/wiki/Key:surface




Van: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> namens lig fietser <ligfietser@hotmail.com>
Verzonden: maandag 6 februari 2017 01:40:46
Aan: mkgmap-dev@lists.mkgmap.org.uk
Onderwerp: Re: [mkgmap-dev] Is smoothness=bad unpaved?
 

Thanks Gerd!



Hi,

if I got that right the forum agreed to this, so if nobody complains I'll
change the default
style as suggested on thursday.

Gerd

ligfietser wrote
> 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' }