
On Sun, Mar 31, 2013 at 12:38:25AM +0100, Enrico Liboni wrote:
Back to the POI I was experiencing the issue with, if I try to reach it now, the device does not try even to calculate the route, as if the POI was really not defined correctly. If I navigate to another POI in front of the former or to the address where the problematic POI is it works just fine so there must be something wrong with it, maybe that's the issue/bug I refer to in my first email... it would be nice to prove this (i.e. if the POI is placed outside the proper polygon).
Look at the ways around the POI. Could the nearest routeable way be a routing island (not connected to the rest of the road network, for example because of a missing junction node)? I experienced this some years ago in the center of Helsinki. One POI was reachable, because there was a highway=residential near it. Another POI next door (some 20 meters away) was not reachable, because it was in a highway=pedestrian area, which at that time was not translated as a routeable line. The nearest routeable way was some corridor in a shopping mall, which ended at the boundary of the highway=pedestrian area. My Garmin Edge 705 would choose the basemap for routing to the 'unreachable' POI, unless I renamed the gmapbmap.img to hide it. Best regards, Marko