[OSM-dev] PostGIS dump
jburgess777 at googlemail.com
Sun Mar 25 00:48:08 GMT 2007
On Thu, 2007-03-22 at 19:09 +0000, Jon Burgess wrote:
> On Thu, 2007-03-22 at 18:52 +0000, Martin Spott wrote:
> > Nick Whitelegg wrote:
> > > OK, will run it on dev, probably as a cron job say 24 hours after planet
> > > (I'm guessing 1am on a Thursday morning is unlikely to be a time when dev
> > > is under strain). BTW would anyone else be interested in the postgis dump?
> > I'm rolling my own and I'd be happy to share it. In:
> > http://mapserver.flightgear.org/OSM/
> > there are four files:
> > 1.) The plain SQL script: planet-070321.sql.bz2
> > 2.) the corresponding PostGIS dump of planet_osm_line, planet_osm_point
> > and planet_osm_polygon: planet_osm-070321.dump
> > 3.) Shapefiles of two layers:
> > planet_osm_line-070321.tar.bz2
> > planet_osm_point-070321.tar.bz2
> > The planet_osm_polygon didn't make it into a Shapefile because the
> > layer apparently contains objects of different geometry types. I'm
> > looking into this.
> > I plan to offer this a a regular service if people would like to see
> > it happen,
> That sounds good.
> The different geometry type would be due to an anomaly in the polygon
> generation process. The upper layers of code decide which table a given
> way should go to based on the key's, but the way generation process
> determines whether to generate a LINESTRING or GEOMETRY based on whether
> the way is closed (start and end are the same). Hence some LINESTRINGs
> end up in the polygon table. There is no fix for this at the moment.
I've put a change into the experimental version which should ensure that
the polygon table contains only polygons.
More information about the dev