[mkgmap-dev] mkgmap and "memory-full-error"

Thu May 30 09:09:08 BST 2013

There is a workaround for the activity routing, which means you have to use carpool avoidance in the car profile.
This avoids all roads tagged with either access=no OR motorcar=no (dont know what happens with motorcar=yes & access=no).

It really depends now how you use your map. Is it for car navgation or also for cycling? Garmin implemented this carpool avoidance by default in the bicycle profile. Which means that the default rules access=no & bicycle=yes do not longer work as expected in the latest Garmins / Basecamp when you select bicycle as activity (bicycle=yes is ignored).

> I've downgraded my Oregon 450 from firmware 6.xx to 5.50, because this
> was the last firmware without the activity routing. With the activity
> routing the routing of my maps was broken (car routing over steps and
> ignoring of "access=no").
> 
> With the firmware 5.50 the routing was correct again. But after a few
> weeks I get the famous memory-full-error. Now I read that in the past
> several people reported this error with maps made with mkgmap.
> 
> The only advice I found, was to use an recent firmware.
> 
> Is there a known bug in mkgmap? How can I avoid the error?
> 
> Christian