[OSM-dev] applying hourly OSM diffs with osmosis gradually messes up database

Daniel Behr daniel.behr at hzg.de
Mon Aug 1 11:00:07 BST 2011

thanks Peter.
nope, not yet. I thought when I set the BBOX larger than my dataset this 
would be no problem and I read it somewhere that it takes that argument 
for updates, too.

I'll try that on the next run, but how does it behave outside the BBOX 
then? It doesnt matter if the map gets messed up there, but what about 
the database size, doesnt it increase drastically?


Am 01.08.2011 11:49, schrieb Peter Körner:
> Am 01.08.2011 11:16, schrieb Daniel Behr:
>> osmosis --rri workingDirectory=/var/lib/pgsql/.osmosis --simc
>> --write-xml-change "-" |\
>> /opt/osm2pgsql/osm2pgsql -s -a -b "-3500000,3720000,5080000,11940000"\
>> --tablespace-main-data europe --tablespace-main-index europe
>> --tablespace-slim-data europe --tablespace-slim-index europe\
>> -d osm -C 4096 -S /opt/osm2pgsql/default.style -
> Have you tried it without the bbox argument? I'm not sure if bbox works
> with updates, because of problems when nodes get moved out (or into) the
> bbox.
> Peter

More information about the dev mailing list