[OSM-dev] Planet OSM 'bad result during COPY'

Seth Voltz seth.voltz at shiftresearch.com
Thu Apr 15 20:01:34 BST 2010


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

I've searched high and low for a solution to this problem and have found nothing that works. I have successfully imported a CloudMade extract of California into my PostGIS database and rendered tiles from it using the Mapnik scripts. Able to confirm basic functionality, I decided to move up to a full planet import. I have tried 3 planet files (100317, 100401 and 100407) with the same error at different points for each file and sometimes different places for the same file on different runs. No import is able to get past the nodes import. From searching on the forums it at first seemed the error was being caused by duplicate data in the Planet file and running without --slim would bypass the problem. Here is the latest run on the 100401 planet export without slim mode:

- ---------------------------------------------------
#> md5sum planet-100401.osm.bz2
6c8b60c7e5c3de093521ba31f3c634cc  planet-100401.osm.bz2
#> cat planet-100401.osm.bz2.md5 
6c8b60c7e5c3de093521ba31f3c634cc  planet-100401.osm.bz2
#> osm2pgsql --database world --username gis --password --verbose planet-100401.osm.bz2
osm2pgsql SVN version 0.69-exported

Password:
Using projection SRS 900913 (Spherical Mercator)
Setting up table: planet_osm_point
NOTICE:  table "planet_osm_point" does not exist, skipping
NOTICE:  table "planet_osm_point_tmp" does not exist, skipping
Setting up table: planet_osm_line
NOTICE:  table "planet_osm_line" does not exist, skipping
NOTICE:  table "planet_osm_line_tmp" does not exist, skipping
Setting up table: planet_osm_polygon
NOTICE:  table "planet_osm_polygon" does not exist, skipping
NOTICE:  table "planet_osm_polygon_tmp" does not exist, skipping
Setting up table: planet_osm_roads
NOTICE:  table "planet_osm_roads" does not exist, skipping
NOTICE:  table "planet_osm_roads_tmp" does not exist, skipping
Mid: Ram, scale=100

Reading in file: planet-100401.osm.bz2
Processing: Node(61870k) Way(0k) Relation(0k)planet_osm_point - bad result during COPY, data 86767681   \N      \N      \N      \N      \N      \N      \N      \N      \N      \N      \N      \N      \N      \N       \N      \N      \N      \N      \N      \N      \N      \N      \N      \N      \N      \N      \N      \N      \N      \N      \N      \N      \N      Unterdürnbach   \N      \N      \N      \N      \N       \N      village \N      \N      \N      \N      \N      \N      \N      \N      \N      \N      \N      \N      \N      \N      SRID=900913;POINT(1767106.17982627 6203496.15919218)

Error occurred, cleaning up
#> 
- ---------------------------------------------------

Running with slim mode on yields the same errors earlier in the document (around 32000k if memory serves)

My installation is CentOS 5.4 with the latest SVN (20912) osm2pgsql. PostgreSQL 5.4.3 and postgis 1.3.6-1 were installed via Yum from the PGDG84 repository.

Thanks in advance for any help.
— Seth
-----BEGIN PGP SIGNATURE-----
Version: PGP Desktop 9.12.0 (Build 1035)
Charset: windows-1252

wsBVAwUBS8dik8gJWVul8LvVAQh4dQf/Y0JnlKur4WqiddieEBPs2AMtX0qB9j9b
atBEQJgHVOIs4+DFiGohpYUDwi2mITt/CG2sLAOhMb4atrs7xF1dpP/74cZpIY8m
blrieRzP7OENQuPSCQjkoQpoh3ktgUgchysf9MONqxDrEKVWFTTYmIz4KQkcnoXy
RnWmmR6A3KYRlikAscZh9W9q1e+hOyCZhNTxRw4nSzdkUlHXONTwV1LuKMGN9r3s
ypY8hUFXH9JMylVkpU51gZUc168VxE2YVhONdHC/fEUbainHhVy/8HaSUcG8A/U+
dWWps26Hnesskv5dxcv+Iakc6JrndGmICsMNNEPq8p23pXJzqZ+NNw==
=JqEi
-----END PGP SIGNATURE-----




More information about the dev mailing list