<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 Uli,<br><br>I would understand this when the style adds two routable<br>ways for the same OSM way. Garmin maps don't<br>use this trick, so I would not be surprised to see<br>that they can't handle it properly.<br>We already noticed that with the cycleways added by the <br>--make-opposite-cycleways option.<br><br>Gerd<br><br><div>> Date: Mon, 17 Nov 2014 01:28:23 -0700<br>> From: ulibaer@gmail.com<br>> To: mkgmap-dev@lists.mkgmap.org.uk<br>> Subject: Re: [mkgmap-dev] Driving on Trail<br>> <br>> GerdP wrote<br>> > Hi Brian,<br>> > <br>> > I never saw this text on my Oregon. If I got you right, <br>> > you have two routable lines for the same OSM way,<br>> > the device routes you over the way for the car,<br>> > but it displays the info for the sidewalk.<br>> > Could this be the reason?<br>> > <br>> > Gerd<br>> <br>> Hi Gerd,<br>> <br>> i can second this behavior on my etrex Vista. The unit definitely routes on<br>> the sideway/bicycle-way and on the next crossing it tries to route onto the<br>> main road. I don't get it, how it "thinks", i am on the sideway, when there<br>> *is* a road and it is in car mode. :?<br>> <br>> I will try to filter "unwanted" data out of the dataset with osmfilter.<br>> <br>> Declaring the sideways not routeable would render the "route for<br>> pedestrians"-mode useless, i think?<br>> <br>> Uli<br>> <br>> <br>> <br>> --<br>> View this message in context: http://gis.19327.n5.nabble.com/Driving-on-Trail-tp5824491p5824566.html<br>> Sent from the Mkgmap Development mailing list archive at Nabble.com.<br>> _______________________________________________<br>> mkgmap-dev mailing list<br>> mkgmap-dev@lists.mkgmap.org.uk<br>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev<br></div> </div></body>
</html>