Seth Voltz schrieb:
does anyone have an idea how long I
can expect to wait before osm2pgsql completes its execution? What is it
doing?
It's normal that this stage can take up to an day.
As far as I understand it creates the indexes now.
Also, is it safe at this point to start up tile
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Peter,
Good estimate of time, it took about 16 hours to finalize everything and DB
access is significantly faster, which I'm betting is a combination of the
indices and the decreased load from the import process.
My tiles are generating about as
Well, the misconfigured RAM cap was the last missing piece, osm2pgsql seems to
have all the resources it requires. The last question I have is one of time. As
of an hour ago I've been running the import for 5 days solid. Around 8 hours
ago I thought the run was complete as it spat out the last
-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
Seth,
just a hunch and it really shouldn't happen but is it possible that
you have an issue with non-ascii characters (which are unlikely in the
california extract but certain to exist in the world-wide data)?
You could quickly try e.g. the Austria excerpt (which should contain the
I've downloaded the Austrian extract and have been running the import for a few
minutes. I'll report back if it succeeds or fails. I should have plenty of RAM
(a blade with 16GB available).
I've seen a number of forum posts about using the -C (cache) flag during
imports. How much does this
Hi
A reasonable value for --cache is 4GB for a planet import. I don't think
that 4GB will be reached but if your server has it..
Peter
Seth Voltz schrieb:
I've downloaded the Austrian extract and have been running the import
for a few minutes. I'll report back if it succeeds or fails. I
On Thu, Apr 15, 2010 at 8:01 PM, Seth Voltz
seth.vo...@shiftresearch.com wrote:
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.
PostgreSQL 5.4.3? that seems awfully old. are you sure?
Matt Amos schrieb:
On Thu, Apr 15, 2010 at 8:01 PM, Seth Voltz
seth.vo...@shiftresearch.com wrote:
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.
PostgreSQL 5.4.3? that seems
On Thu, 2010-04-15 at 12:01 -0700, Seth Voltz wrote:
-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
Jon and Frederik: good hunch, the Austrian import failed with:
# osm2pgsql --database world --username gis --password --verbose
austria.osm.bz2
... (cut) ...
Reading in file: austria.osm.bz2
Processing: Node(6760k) Way(0k) Relation(0k)planet_osm_point - bad
On Thu, 2010-04-15 at 14:24 -0700, Seth Voltz wrote:
Jon and Frederik: good hunch, the Austrian import failed with:
# osm2pgsql --database world --username gis --password --verbose
austria.osm.bz2
... (cut) ...
Reading in file: austria.osm.bz2
Definitely worth checking out. When I setup the system I didn't install any of
the CentOS Postgres packages and instead relied on the pgdg84 available ones.
---
# ldd /usr/local/bin/osm2pgsql | grep libpq
libpq.so.5 = /usr/lib64/libpq.so.5 (0x2aab6b07c000)
13 matches
Mail list logo
