Felix Hartmann-2 wrote > 3) Take it out of the address index? I'm not sure if 2) is better or > not. In the above featured way, there is no error in OSM, hence I would > say better have the map looking correct, and one address not findable, > than have the map looking wrong. > The best solution would be a table where all routable lines are defined, > with their nonroutable counterpart - that would be very complex however. > > For my maps, I would prefer 3) - dropping the street from the address > index.
I think option 3 is what happens now. The road is not added to the list of roads, it is treated like any other non-routable line (by mkgmap) and my understanding is that this should be avoided. Gerd -- View this message in context: http://gis.19327.n5.nabble.com/No-roads-near-target-bug-in-Schwabmunchen-tp5753364p5757141.html Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list [email protected] http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
