basemap routing is used instead of the mkgmap derived map
Can anyone confirm this bug? https://github.com/maning/osmphgps/issues/20 On my test, when using the `Address` to find streets and chose to route, it uses the basemap instead of the osm mkgmap data. (See sample screenshots reported by the user) -- cheers, maning ------------------------------------------------------ "Freedom is still the most radical idea of all" -N.Branden wiki: http://esambale.wikispaces.com/ blog: http://epsg4253.wordpress.com/ ------------------------------------------------------
On Fri, Jun 17, 2011 at 06:59:09PM +0800, maning sambale wrote:
Can anyone confirm this bug? https://github.com/maning/osmphgps/issues/20
I reported this several months ago. In my case, the problem was a "routing island". The destination way was not connected to the rest of the road network. (It was on a highway=pedestrian area; I fixed it by adding a way through the area.) If I renamed the gmapbmap.img so that Garmin would be unable to find it, then it would say "routing error". The destination point happened to be on a way in the Garmin basemap, that is apparently why it chose the basemap. If I routed to the next POI (some 20 meters apart), it would route just fine, using a way that was connected to the edge of the pedestrian area. I guess that Garmin picks the nearest way to the destination POI and computes the route backwards from that. If the nearest way is a "routing island", it will not work. Does http://keepright.ipax.at cover the area? Does it report any "routing islands" near the start or destination? Best regards, Marko
Dear Marko, I don't think it is "way island problem". I've seen this behaviour on several areas but the data is OK. On 6/17/11, Marko Mäkelä <marko.makela@iki.fi> wrote:
On Fri, Jun 17, 2011 at 06:59:09PM +0800, maning sambale wrote:
Can anyone confirm this bug? https://github.com/maning/osmphgps/issues/20
I reported this several months ago. In my case, the problem was a "routing island". The destination way was not connected to the rest of the road network. (It was on a highway=pedestrian area; I fixed it by adding a way through the area.)
If I renamed the gmapbmap.img so that Garmin would be unable to find it, then it would say "routing error". The destination point happened to be on a way in the Garmin basemap, that is apparently why it chose the basemap. If I routed to the next POI (some 20 meters apart), it would route just fine, using a way that was connected to the edge of the pedestrian area.
I guess that Garmin picks the nearest way to the destination POI and computes the route backwards from that. If the nearest way is a "routing island", it will not work.
Does http://keepright.ipax.at cover the area? Does it report any "routing islands" near the start or destination?
Best regards,
Marko _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- cheers, maning ------------------------------------------------------ "Freedom is still the most radical idea of all" -N.Branden wiki: http://esambale.wikispaces.com/ blog: http://epsg4253.wordpress.com/ ------------------------------------------------------
participants (2)
-
maning sambale -
Marko Mäkelä