
I drove to work with OSM data via mkgmap in my GPS V, and noticed that it seemed very sluggish. When I got to Cambridge I could see the outlines of all the buildings, including houses! These are simple closed ways with building=yes. http://www.openstreetmap.org/?lat=42.3916&lon=-71.14961&zoom=15&layers=B000F... I wonder if the GPS V can't really handle that many area features. It seems best to omit areas with building=yes, or at least building=yes w/o name=something.

On Thu, Apr 16, 2009 at 2:56 PM, Greg Troxel <gdt@ir.bbn.com> wrote:
I drove to work with OSM data via mkgmap in my GPS V, and noticed that it seemed very sluggish. When I got to Cambridge I could see the outlines of all the buildings, including houses!
These are simple closed ways with building=yes.
http://www.openstreetmap.org/?lat=42.3916&lon=-71.14961&zoom=15&layers=B000F...
I wonder if the GPS V can't really handle that many area features.
It seems best to omit areas with building=yes, or at least building=yes w/o name=something.
You can do this by pre-processing the OSM data before you make a .img out of it.
participants (2)
-
Greg Troxel
-
Ævar Arnfjörð Bjarmason