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

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

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

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' }
________________________________ Van: mkgmap-dev <
mkgmap-dev-bounces@.org
> namens Gerd Petermann <
GPetermann_muenchen@
> 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@.org
> im Auftrag von lig fietser <
ligfietser@
> 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@.org
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n8.nabble.com/Is-smoothness-bad-unpaved-tp5890167p5890637.h... Sent from the Mkgmap Development mailing list archive at Nabble.com.

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' } <http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev>

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' } <http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev>

Hi,
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!
Rule is OK. If you negate conjunction (by use of "unless"), then you should use disjunction of negations: highway is unpaved when there is *no* surface and *no* tracktype and ... equivalent: highway is unpaved unless there is surface or tracktype or ... -- Best regards, Andrzej

Thanks Andrzej, I got a bit confused there. The issue was caused by the generic new typ file that marked the track line type as 'unpaved road' . Should be better if I use 'track' or add another label 'paved' to it. Van: Andrzej Popowski Verstuurd: dinsdag 7 februari 00:46 Onderwerp: Re: [mkgmap-dev] Is smoothness=bad unpaved? Aan: Development list for mkgmap Hi, > 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! Rule is OK. If you negate conjunction (by use of "unless"), then you should use disjunction of negations: highway is unpaved when there is *no* surface and *no* tracktype and ... equivalent: highway is unpaved unless there is surface or tracktype or ... -- Best regards, Andrzej _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
participants (4)
-
Andrzej Popowski
-
Gerd Petermann
-
Gerd Petermann
-
lig fietser