<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta content="text/html; charset=UTF-8">
<style type="text/css" style="">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:#000000; font-family:Calibri,Arial,Helvetica,sans-serif">
<p>Good job Gerd,</p>
<p>Two remarks:</p>
<p><br>
</p>
<p>mtb:scale=0 can also be used for paved trails. I would suggest not to assume this means unpaved if mkgmap:unpaved=0</p>
<p>So better use this rule >0 and 0+</p>
<p><br>
</p>
<p>I guess bridleways can be paved too, so also apply this for mkgmap:unpaved!=0<br>
</p>
<p><br>
</p>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>Van:</b> mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> namens Gerd Petermann <GPetermann_muenchen@hotmail.com><br>
<b>Verzonden:</b> donderdag 9 februari 2017 08:58:58<br>
<b>Aan:</b> Development list for mkgmap<br>
<b>Onderwerp:</b> Re: [mkgmap-dev] [Patch] unpaved roads</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">reg. smoothness: the patch contains this line , forgot to comment it<br>
Rule 7:<br>
highway=* & mkgmap:unpaved!=1 & smoothness ~ '.*(bad|horrible|impassable)' { add mkgmap:road-speed = '-2' }
<br>
<br>
reg. double values: I agree that most of them come from wrongly merged roads.<br>
The patch treats them all as unpaved, the unpatched version treats them like paved.<br>
I think the patch makes it more likely that someone will fix the wrong value(s), and it is producing fewer
<br>
errors.<br>
I see no reason to believe that the first value is better than the 2nd.<br>
<br>
Gerd<br>
________________________________________<br>
Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Alexandre Folle de Menezes <afmlistas@terra.com.br><br>
Gesendet: Donnerstag, 9. Februar 2017 17:45:46<br>
An: Development list for mkgmap<br>
Betreff: Re: [mkgmap-dev] [Patch] unpaved roads<br>
<br>
Great, but now you are not handling smoothness anymore.<br>
<br>
Regarding the double values, i would get the first and ignore all the rest. I believe these come from wrongly merging segments with different surfaces, there's no way to know which one is correct.<br>
<br>
Best regards,<br>
<br>
Alexandre<br>
<br>
Em 09/02/2017 13:43, Gerd Petermann escreveu:<br>
<br>
Okay, attached is v6 (more or less a mixture of v2 and v3)<br>
<br>
Some comments:<br>
Rule 1) surface values meaning paved:<br>
highway=* & (surface=asphalt | surface=paved | surface=sett |<br>
surface=concrete | surface=concrete:lanes | surface=concrete:plates |<br>
surface=paving_stones | surface=cobblestone |<br>
surface=cobblestone:flattened | surface=metal | surface=wood)<br>
{ set mkgmap:unpaved=0 }<br>
<br>
Rule 2) tracktype=grade1 without explicit surface implies paved:<br>
highway=* & tracktype=grade1 & surface!=* { set mkgmap:unpaved=0 }<br>
<br>
Rule 3) highway which was not set to paved before and has a surface or valid tracktype tag is unpaved:<br>
highway=* & mkgmap:unpaved!=0 & ( surface=* | tracktype ~ 'grade[2-6]') { add mkgmap:unpaved=1 }<br>
<br>
Rule 4) highway with mtb:scale or climbing attributes is unpaved, even if surface says paved:<br>
highway=* & (<br>
mtb:scale=* |<br>
sac_scale ~ '.*(mountain|alpine)_hiking' |<br>
sport=via_ferrata)<br>
{ set mkgmap:unpaved=1 }<br>
Rule 5) default for hw= path or track is unpaved:<br>
(highway=path | highway=track) & mkgmap:unpaved!=0 { add mkgmap:unpaved=1 }<br>
Rule 6) set special highway types to unpaved even if surface says paved:<br>
(highway=bridleway | highway=unsurfaced | highway=via_ferrata) { set mkgmap:unpaved=1 }<br>
<br>
I am not 100% sure about hw=bridleway in rule 6. I think horses don't like paved ways, so a paved<br>
bridleway is probably a tagging error.<br>
<br>
I am quite happy with this.<br>
<br>
Does anybody know a good way to handle tags with lists like these?<br>
1) surface=asphalt;paving_stones (all meaning paved)<br>
2) surface=grass;earth (all meaning unpaved)<br>
3) surface=asphalt;sand (mixed)<br>
<br>
Taginfo shows that most values containing a semicolon are of type 2 or 3.<br>
Maybe rule 1 should also contain asphalt;paving_stones , asphalt;paved and paved;asphalt<br>
<br>
Please suggest improvements, else I'll commit this patch on Monday.<br>
<br>
Gerd<br>
________________________________________<br>
Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk><mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Carlos Dávila <cdavilam@orangecorreo.es><mailto:cdavilam@orangecorreo.es><br>
Gesendet: Donnerstag, 9. Februar 2017 14:02:05<br>
An: Development list for mkgmap<br>
Betreff: Re: [mkgmap-dev] [Patch] unpaved roads<br>
<br>
I would interpret that the other way round. If surface=paved, concrete,<br>
... treat it as paved, no matter what tracktype is. I think tracktype is<br>
very often misinterpreted by mappers, and wiki doesn't clarify it much<br>
either. Additionally, tracktype>1 may be an old tag placed before track<br>
was paved, in the same way that you can find a lot of<br>
highway=residential, tertiary, etc + tracktype=*<br>
<br>
El 09/02/17 a las 11:25, lig fietser escribió:<br>
<br>
<br>
<br>
My OFM will mark them as unpaved. The combination of track and grade3<br>
counts more than the surface. I think the current default rules assign<br>
them also as unpaved. Your patch v3 too, is that correct?<br>
<br>
<br>
<br>
------------------------------------------------------------------------<br>
Gerd wrote:<br>
<br>
And what about combinations of surface meaning paved with tracktype?<br>
The wiki says "Usually ... " or "Almost always an unpaved track" for most<br>
tracktype values.<br>
<br>
I see quite a lot of ways with<br>
highway=track & surface=concrete:lanes & tracktype=grade3<br>
in my Niedersachsen:<br>
<a href="http://overpass-turbo.eu/s/lNI">http://overpass-turbo.eu/s/lNI</a><br>
<br>
I think those are not unpaved, no matter how nice it is to cycle on<br>
them;-)<br>
<br>
Gerd<br>
<br>
<br>
<br>
_______________________________________________<br>
mkgmap-dev mailing list<br>
mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk><br>
<a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
mkgmap-dev mailing list<br>
mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk><br>
<a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br>
<br>
_______________________________________________<br>
mkgmap-dev mailing list<br>
mkgmap-dev@lists.mkgmap.org.uk<br>
<a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br>
</div>
</span></font>
</body>
</html>