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