<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 Minko,<br><br>okay, I have to try that. My understanding is that address search knows only <br>routable ways (those that appear in NOD). And to NOD we write <br>all lines with road_class/road_speed attribute and a non-extended type.<br>Maybe Garmin software expects (or expected) to find NOD data for <br>all lines with routable types.<br><br>Gerd<br> <br><br><br><div>> Date: Fri, 2 May 2014 15:11:57 +0200<br>> From: ligfietser@online.nl<br>> To: mkgmap-dev@lists.mkgmap.org.uk<br>> Subject: Re: [mkgmap-dev] strange routing<br>> <br>> Gerd,<br>> It happens when you search for an address that is located at a line which is routable,<br>> but made non-routable for some reason (for instance if bicycle=no, someone who makes a bike map wants to remove the road parameters for a line like highway=secondary [0x04 resolution 20]<br>> This was done because of bicycle=no was not recognized anymore by Basecamp (until recently).<br>> On the osm forum there are some examples.<br>> <br>> http://forum.openstreetmap.org/viewtopic.php?pid=208081#p208081<br>> http://forum.openstreetmap.org/viewtopic.php?id=13884&p=5<br>> <br>> I dont know it is still the case with the latest releases.<br>> <br>> <br>> > Onderwerp: Re: [mkgmap-dev] strange routing<br>> > Hi Felix,<br>> > <br>> > on the other hand, the test that prints the messages below may also be<br>> > out-dated.<br>> > I am no longer sure that the use of routable types for non-routable<br>> > lines really breaks<br>> > routing. I'll have to search the archives to find out why I've coded<br>> > that test.<br>> > <br>> > Gerd<br>> <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>