When I tested routing after moving most points to resolution 24, I hit a big surprise. I let my Edge 705 calculate the route to this shop=organic: http://www.openstreetmap.org/browse/node/370814886 To my great surprise, Garmin used the base map for computing the route, no matter which mode of transportation I chose. I thought that maybe my map tile has grown too big, but splitting it into three did not help. Then, I tried routing to some nearby points, such as the bus station http://www.openstreetmap.org/browse/node/59967454, and that worked. I can navigate to that point even when using a single map tile. I wonder what is causing this? That the shop=organic could be located exactly on a way on the basemap? One more interesting point is that I did this calculation in demo mode, from about http://www.openstreetmap.org/?lat=60.3491678&lon=25.1092643&zoom=18. When the route used the base map, this position jumped to about http://www.openstreetmap.org/?lat=60.3473225&lon=25.1271307&zoom=18 which was close to the way (ref=140) on the basemap. I have successfully calculated a route to the shop before, but that was with an older basemap. The old basemap displayed a toilet symbol near my house; that's why I know. :-) Regards, Marko
I can't answer your question but I can say that I removed the base map from my 605 months ago. If it doesn't exist it can't be used and the base map on my 605 was practically useless anyway Cheers Paul On 06/02/11 20:03, Marko Mäkelä wrote:
When I tested routing after moving most points to resolution 24, I hit a big surprise. I let my Edge 705 calculate the route to this shop=organic:
http://www.openstreetmap.org/browse/node/370814886
To my great surprise, Garmin used the base map for computing the route, no matter which mode of transportation I chose. I thought that maybe my map tile has grown too big, but splitting it into three did not help. Then, I tried routing to some nearby points, such as the bus station http://www.openstreetmap.org/browse/node/59967454, and that worked. I can navigate to that point even when using a single map tile.
I wonder what is causing this? That the shop=organic could be located exactly on a way on the basemap? One more interesting point is that I did this calculation in demo mode, from about http://www.openstreetmap.org/?lat=60.3491678&lon=25.1092643&zoom=18. When the route used the base map, this position jumped to about http://www.openstreetmap.org/?lat=60.3473225&lon=25.1271307&zoom=18 which was close to the way (ref=140) on the basemap.
I have successfully calculated a route to the shop before, but that was with an older basemap. The old basemap displayed a toilet symbol near my house; that's why I know. :-)
Regards,
Marko _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
On Sun, Feb 06, 2011 at 10:51:43PM +0000, Paul wrote:
I can't answer your question but I can say that I removed the base map from my 605 months ago. If it doesn't exist it can't be used and the base map on my 605 was practically useless anyway
Without a basemap, the 705 says 'error in route calculation' straight away. If I click on the Aussie bar next door (some 10 or 20 m away), it will calculate a route. Could the error be that an access=private highway=service on layer=-1 is closest to the point, and Garmin fails to choose another road? (Usually, the routing algorithm seems to want to go to the nearest road, and then the shortest distance from the road to the point.) I guess that the fix is to draw a cycleway across the highway=pedestrian area, in front of the shop. That should take care of this, and also allow better routing in the area. BTW, is there an easy way to remove the highways from the basemap? The coastline is somewhat useful. Without a basemap, one cannot see the tile borders when zooming out. Marko
"Marko Mäkelä" marko.makela@iki.fi wrote on 07/02/2011 at 07:03:28 +1100 subject "[mkgmap-dev] Base map interfering with routing" :
When I tested routing after moving most points to resolution 24, I hit a big surprise. I let my Edge 705 calculate the route to this shop=organic:
.../...
I have successfully calculated a route to the shop before, but that was with an older basemap. The old basemap displayed a toilet symbol near my house; that's why I know. :-)
The word "before" is probably the problem. In nuvi I figured out that the "Recent Finds" do sometimes not work correctly after updating the gmapsupp.img This seems to affect the routing even if you select the destination in the normal POI categories not only by selecting is in the recent finds folder. My oregon 550 has not the possibility to empty the "recent finds", but I never had this routing errors on this device. This engendered an issue similar to the one you are describing. I now empty the recent finds folder immediately after updating my gmapsupp.img and I dit not hove this errors since then. See http://www.mail-archive.com/mkgmap-dev@lists.mkgmap.org.uk/msg06479.html for the description of the error I had. I suspect that the nuvi is giving some id number to each POI and if the gmapsupp.img is updated, the id number are not the same anymore, and an formerly existing id number will be attributed to an other POI. And this makes the routing fail. -- Sincerely Hendrik Oesterlin - email hendrikmail2002@yahoo.de
On Wed, Feb 09, 2011 at 05:44:07AM +1100, Hendrik Oesterlin wrote:
"Marko Mäkelä" marko.makela@iki.fi wrote on 07/02/2011 at 07:03:28 +1100 subject "[mkgmap-dev] Base map interfering with routing" :
When I tested routing after moving most points to resolution 24, I hit a big surprise. I let my Edge 705 calculate the route to this shop=organic:
.../...
I have successfully calculated a route to the shop before, but that was with an older basemap. The old basemap displayed a toilet symbol near my house; that's why I know. :-)
The word "before" is probably the problem. In nuvi I figured out that the "Recent Finds" do sometimes not work correctly after updating the gmapsupp.img
No, I actually tried that months before, on a different device that had a slightly different basemap. A button stopped clicking, and I returned the device for warranty service, a couple of weeks before the end of the 2-year warranty period. The new try was on the replacement device, with originally clean history, but admittedly with some gmapsupp.img upgrades. The "Recent Finds" menu is often corrupted after a gmapsupp.img upgrade on the Edge 705. When I dare to select an item in the menu, the device may crash or at least lose the map until the next reboot. But I was using the Shops/Special menu.
This seems to affect the routing even if you select the destination in the normal POI categories not only by selecting is in the recent finds folder.
I have never experienced anything like that. Only the Recent Finds menu gives trouble for me. I suspect that the problem was that the nearest way to the POI was a routing island, not reachable from the rest of the map (including the source point). I added some bicycle=yes footways across the highway=pedestrian area. (That should not have been a sin, because the bicycle route is marked on the plaza.) Let me retry with those ways in place. Yes, it works, using the way that I added.
My oregon 550 has not the possibility to empty the "recent finds", but I never had this routing errors on this device.
My Edge 705 empties it as part of a full memory erase or firmware upgrade. :-) Marko
The "Recent Finds" menu is often corrupted after a gmapsupp.img upgrade on the Edge 705. When I dare to select an item in the menu, the device may crash or at least lose the map until the next reboot. But I was using the Shops/Special menu.
The 605 is similar in this respect although I wouldn't call it corrupted. I too presumed that the POIs had a different index number each time I regenerated the gmapsupp.img as any POI I searched for from the Find Places was always different. Any location I've saved as a favourite however is still fine and works as expected. I've never had it crash when choosing a "changed" POI though. Cheers Paul
Looks like I have the same problem now. :-( I was testing a map created with mkgmap-r1827. It was a combined map with tiles from two mapsets with different family ID's (The Netherlands and Germany). With mkgmap I copied a few img's to a different directory and created a new map with another FID. It looked good in Mapsource. Then I send it to the Nuvi. I searched for "Osnabruck" and started to route from Enschede. Since then the route navigates only via the Basemap, not the osm map anymore. Tried to rename the basemap, but then routing isnt possible anymore. Hard resetting the unit: no solution, it keeps routing via the basemap. If I turn CN on, it follows the CN roads, so that looks ok. I tried different and older osm maps, but it still routes via the basemap. I replaced CN (a gmapsupp.img) by another gmapsupp.img (osm map) on the internal memory card but it didnt seem to navigate via the osm roads, just the basemap. This doesn't look good. Maybe it has to do with the latest revisions? (mkgmap-r1827). I have tried this before with other mkgmap versions but never had such problems. Regards, Minko
Minko schreef:
After reflashing the firmware the routing problems have gone....
Just a remark - I don't know if it would have been useful for your situation. When I build maps, I increment the "mapname" parameter automatically: --mapname=3100${mapid} where mapid is variable that I increment each time I run mkgmap. I did this because I saw my Garmin Nüvi crash whenever I used a new map with the same map-number as the old map. I concluded that the Nüvi probably does some sort of caching of it's current map, and got confused whenever the map had changed but the map number had not. So I don't know if this is identical to your situation; next time, you might want to try a map with a different "mapname" and see if it will route again. Best regards, Valentijn
On 10/02/11 16:54, Minko wrote:
After reflashing the firmware the routing problems have gone.... _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Funnily enough I had problems with excessive battery usage on my 605 which seem to have been fixed by re-applying the latest firmware. Now that I think about it I also had a couple of crashes whilst recording which I've not had since re-applying as well Hmmmmmmmmmmmmmm Cheers Paul
participants (5)
-
Hendrik Oesterlin -
Marko Mäkelä -
Minko -
Paul -
Valentijn Sessink