I have made some screenshots for this weird routing behaviour: http://sites.google.com/site/openfietsmap/routing
Conclusions: -If two routable lines are combined, routing breaks when address search is used (btw I have used mkgmap-locator-r1912.jar, same happened with previous version) -Instead of routing to the destination, the route goes to the end of the tile, and from there a direct straight line to the destination -If you point to the same road on the map, routing is fine The reason why I use two routable lines is because 0x01 and 0x02 have a very high draw priority so it is displayed under all circumstances on top of any other line. So this makes it convenient to indicate bike routes or no bicycle allowed roads. ----- Oorspronkelijk bericht ----- I've noticed that routing breaks if I search for an address, where the street consists of multiple lines in the style file. For instance a tertiary road plus a tunnel. Or a bike path with a cycle route. In those cases both lines were routable. In cases where I use overlay lines (with the continue statement) that are non routable, routing doesn't seem to break. On Mapsource or on the GPS it routes fine if you point to that road on the map. With the address search on the GPS however, the street is found but if i want to calculate a route, the device says either 'there are no routable streets' or the route makes very weird jumps to the tile end and bounces back to to the destination in a straight line. I think I can prevent this behaviour by using non-routable lines for overlays, but maybe some improvements can be made in the mkgmap code? _______________________________________________ mkgmap-dev mailing list [email protected] http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list [email protected] http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
