<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 Andrzej,<br>> <br><div>> I wouldn't say it is a small problem. Any car route to or from an <br>> address, which happened to be on a one-way road with opposite cycleway, <br>> could lead you wrong-way.<br><br>OK, did not see that before, but you are right. That is really a "no go".<br>> <br>> Consider area near your test route. I see at least 10 cycleways nearby, <br>> maybe 20-30% of addresses is affected in this area.<br>> <br>> Have you noticed, that car route for your example is wrong-way too?<br><br>No, but I did not care as I selected the bicycle ways.<br><br>I also did not notice that Basecamp - unlike MapSource - doesn't allow <br>to select the way (car or bicycle), at least I did not find out how,<br>so it always choses the first way :-(<br>That makes it likely that the device will also select the wrong type of way.<br><br>Conclusion:<br>- No matter what method we use either car or bicycle routing is not perfect<br>(this is also true for styles that use continue to create additional ways)<br>- Until that is solved by Garmin, I agree that we should prefer correct car routing <br>and accept detours for bicycles in a general purpose map, so the car road should <br>come first.<br><br>Attached is version 6 of the patch which is like v5, just reverses the order of ways.<br><br>Besides, I would prefer to add a few lines to the default style and remove both<br>all hard coded make-cycleway options.<br><br>Gerd<br><br><br><br><br></div> </div></body>
</html>