[OSM-talk] Graphical generation of Garmin maps from OSM data

[Martin Spott]

Kristian Thy wrote:
> On Fri, Dec 22, Martin Spott wrote:
> > you might consider to join forces, make one step ahead and write a
> > driver for GDAL/OGR:
> > 
> >   http://www.gdal.org/ogr/
> > 
> > This toolset already implements almost every aspects of what you exect
> > from a "babel" translator in the world of geographic vector data.

> My primary motivation for doing a separate conversion script was to do
> some preprocessing - i.e. convert lakes into polygons instead of line
> features, creating a separate "amenity" point layer and so on. If you do
> an OGR plugin, I presume you'll only be able to access an OSM file as a
> line feature? (I'm not totally up to speed on multigeometry classes,
> though, so this may be wrong.)

OGR is able to handle at least the common geometry types like POINT,
LINE, MULTILINE, POLYGON, MULTIPOLYGON - these are the ones _I_ use OGR
for, there may be some more.
Additionally you can attach numerous different attributes of your
choice to every object that you want OGR to handle. In Shapefiles these
attributes are stored in a DBASE-type file and referenced from the
geometry file, in PostGIS these are just additional columns in a table,

Martin.
-- 
 Unix _IS_ user friendly - it's just selective about who its friends are !
--------------------------------------------------------------------------