<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Hi Mike,<br><br>as I said, I'd be more happy to have a patch that remove's the option<br>and shows how to change the default style instead to get the same result <br>as with your patch.<br><br>Your patch tries to remove all kinds of tags which might lead to wrong<br>routing:<br>+ cycleWay.deleteTag("vehicle");<br>+ cycleWay.deleteTag("motor_vehicle");<br>+ cycleWay.deleteTag("carpool");<br>+ cycleWay.deleteTag("delivery");<br>+ cycleWay.deleteTag("emergency");<br>+ cycleWay.deleteTag("foot");<br>+ cycleWay.deleteTag("goods");<br>+ cycleWay.deleteTag("hgv");<br>+ cycleWay.deleteTag("motorcar");<br>+ cycleWay.deleteTag("motorcycle");<br>+ cycleWay.deleteTag("psv");<br>+ cycleWay.deleteTag("route");<br>+ cycleWay.deleteTag("taxi");<br>+ cycleWay.deleteTag("bus");<br>+ cycleWay.deleteTag("truck"); <br><br>Please explain why you remove route=* .<br>I think that one should be kept.<br><br>Gerd<br><br><br><div><hr id="stopSpelling">From: mike@tvage.co.uk<br>To: mkgmap-dev@lists.mkgmap.org.uk<br>Date: Tue, 3 Mar 2015 19:45:00 +0000<br>Subject: Re: [mkgmap-dev] --make-opposite-cycleways option<br><br><style><!--
.ExternalClass p.ecxMsoNormal, .ExternalClass li.ecxMsoNormal, .ExternalClass div.ecxMsoNormal {
font-size:12.0pt;
font-family:"Times New Roman",serif;
}
.ExternalClass a:link, .ExternalClass span.ecxMsoHyperlink {
color:#0563C1;
text-decoration:underline;
}
.ExternalClass span.ecxMsoHyperlinkFollowed {
color:#954F72;
text-decoration:underline;
}
.ExternalClass p {
font-size:12.0pt;
font-family:"Times New Roman",serif;
}
.ExternalClass pre {
font-size:10.0pt;
font-family:"Courier New";
}
.ExternalClass span.ecxHTMLPreformattedChar {
font-family:"Consolas",serif;
}
.ExternalClass span.ecxEmailStyle20 {
font-family:"Calibri",sans-serif;
color:#1F497D;
}
.ExternalClass span.ecxSpellE {
}
.ExternalClass .ecxMsoChpDefault {
font-size:10.0pt;
}
.ExternalClass div.ecxWordSection1 {
}
--></style><div class="ecxWordSection1"><p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;">HI <span class="ecxSpellE">Gerd</span>, the attached updated patch adds a line to the default style that can be uncommented if you want to see the opposite cycleway names as they are currently.</span></p><p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;"> </span></p><p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;">Regards,</span></p><p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;">Mike</span></p><p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;"> </span></p><div><div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm;"><p class="ecxMsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;" lang="EN-US">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;" lang="EN-US"> Gerd Petermann [mailto:gpetermann_muenchen@hotmail.com] <br><b>Sent:</b> 03 March 2015 08:26<br><b>To:</b> mkgmap-dev@lists.mkgmap.org.uk<br><b>Subject:</b> Re: [mkgmap-dev] --make-opposite-cycleways option</span></p></div></div><p class="ecxMsoNormal"> </p><div><p class="ecxMsoNormal" style=""><span style="font-family:"Calibri",sans-serif;">Hi Mike,<br><br>I think you are right regarding the access tags.<br>The current solution in combination with the default style<br>might route a truck through the wrong direction of a oneway.<br>Thanks for pointing this out.<br><br>If I got it right, most style developers don't use this option,<br>they prefer to have the logic in the rules.<br>Maybe this is another argument to remove the option<br>instead of adding code to make it work in special cases?<br><br>Is anybody able to change the default style so that it produces<br>the same result ?<br><br>Gerd</span></p><div><p class="ecxMsoNormal" style=""><span style="font-family:"Calibri",sans-serif;">From: <a href="mailto:mike@tvage.co.uk">mike@tvage.co.uk</a><br>To: <a href="mailto:mkgmap-dev@lists.mkgmap.org.uk">mkgmap-dev@lists.mkgmap.org.uk</a><br>Date: Mon, 2 Mar 2015 22:46:07 +0000<br>Subject: [mkgmap-dev] --make-opposite-cycleways option</span></p><pre>Dear all,<br> <br>When using the --make-opposite-cycleways option, I notice that the address<br>index adds a road name of the actual road name suffixed with " (cycleway)".<br>For me at least, this is undesirable. Also the generated name does not<br>conform to the OSM naming convention of not including any descriptive<br>information in names. I therefore propose that the name of an opposite<br>cycleway be set to the same as the original road name, and that users who<br>want to name the opposite cycleway differently should use the style file to<br>rename it.<br> <br>In looking at the code that produces the opposite cycleway, I also believe<br>there is an error in the way it handles access tags - the code currently<br>sets access=no, bicycle=yes and foot=no, but ignores all other access tags.<br>Hence if (for example) the road has psv=yes on it, the generated cycleway<br>will also have psv=yes (unless I am misunderstanding something in the<br>handling of access tags). <br><span style=""> </span><br>I therefore submit the attached patch for trial.<br> <br>Regards,<br>Mike</pre><p class="ecxMsoNormal"><span style="font-family:"Calibri",sans-serif;"><br>_______________________________________________ mkgmap-dev mailing list <a href="mailto:mkgmap-dev@lists.mkgmap.org.uk">mkgmap-dev@lists.mkgmap.org.uk</a> <a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev" target="_blank">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a></span></p></div></div></div><br>_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</div> </div></body>
</html>