[OSM-dev] Using NULL values in mapnik / postgres DB

Artem Pavlenko artem at pavlenko.uklinux.net
Sat Feb 24 08:55:39 GMT 2007


I had a go:) . Changes in svn.  Latest osm2pgsql requires geos (I'm using 
latest trunk http://svn.refractions.net/geos/trunk). 

TODO: 
1. output wkb(hex) instead of wkt
2. build polygons with holes.
3. investigate why geos fails to clean 4067050 and 4229618

Cheers,
Artem
 
On Wednesday 21 February 2007 23:50, Jon Burgess wrote:
> On Wed, 2007-02-21 at 21:53 +0000, Artem Pavlenko wrote:
> > Hello,
> >
> > Attached is console app that takes list of geometries ( in WKT format)
> > and cleans them. It works quite well and I can correct all not simple
> > ways from latest osm. It requires GEOS lib from geos.refractions.net (I'm
> > using geos-3.0.0rc3).
> >
> > It should fit nicely into osm2pgsql as in essence it takes bunch of
> > segments, 'node' them , merge them and spits out 'clean' geometries.
> >
> > As a side effect it is possible to output geometries in HEX WKB format
> > which will speed up loading into postgresql.
> >
> > Shall I try to merge this into osm2pgsql?
> >
> > Cheers,
> > Artem
>
> Feel free to have a go. I guess the easiest thing would be to wrap your
> C++ code with extern "C" and then link and call it from the C code.
>
> Otherwise there is a C API to Geos (it even seems to be recommended over
> the C++ for API stability).
>
> 	Jon




More information about the dev mailing list