[osmosis-dev] proper usage of osmosis when writing changes to osm api db
Hi all I'd like to create the local copy of osm api db. First I populated DB with full planet.osm file using osmosis, afterwards initialized and created osm change file. Should I run --simplify-change before applying the change file to the db? I.e. is it required nice gzip -d -c change.osm.gz | nice ./osmosis --read-xml-change file=/dev/stdin --simplify-change --write-xml-change file=- | nice gzip -9 -c > change.unique.osm.gz Thanks -- Dmytro Korochkin Senior Analyst of IT Operations Cogniance Inc ___ osmosis-dev mailing list osmosis-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/osmosis-dev
Re: [osmosis-dev] proper usage of osmosis when writing changes to osm api db
I'm not sure if this is helpful or not Some of this info may or may not be relevant anymore.. but 1. If you want to load diffs, you need to make sure you load the planet file using --slim mode (which is slower) but is required to apply diffs. 2. This is the syntax I use. I'm not sure why you're gzipping the changes.osc before hand. 2a. download change set: osmosis --read-replication-interval --simplify-change --write-xml-change 2b. write changeset: osm2pgsql --host localhost -e 10 -o expire.list --verbose --append --slim --cache 6144 change.osc the -e 10 and -o expire.list are optional, I use the expire list to re-generate only tiles that are affected. -- Samir On Thu, Dec 9, 2010 at 8:18 AM, Dmytro Korochkin wrote: > Hi all > > I'd like to create the local copy of osm api db. > First I populated DB with full planet.osm file using osmosis, > afterwards initialized and created osm change file. > > Should I run --simplify-change before applying the change file to the db? > > I.e. is it required > nice gzip -d -c change.osm.gz | nice ./osmosis --read-xml-change > file=/dev/stdin --simplify-change --write-xml-change file=- | nice > gzip -9 -c > change.unique.osm.gz > > Thanks > -- > Dmytro Korochkin > Senior Analyst of IT Operations > Cogniance Inc > > ___ > osmosis-dev mailing list > osmosis-dev@openstreetmap.org > http://lists.openstreetmap.org/listinfo/osmosis-dev > -- -- Samir Faci *insert title* fortune | cowsay -f /usr/share/cows/tux.cow ___ osmosis-dev mailing list osmosis-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/osmosis-dev
Re: [osmosis-dev] proper usage of osmosis when writing changes to osm api db
Samir, Samir Faci (Dev) wrote: I'm not sure if this is helpful or not It was well intended but the original author inquired about an API DB database, which is populated directly by osmosis, without osm2pgsql. It uses a different database schema and does not have a "slim" mode. Bye Frederik -- Frederik Ramm ## eMail frede...@remote.org ## N49°00'09" E008°23'33" ___ osmosis-dev mailing list osmosis-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/osmosis-dev
Re: [osmosis-dev] proper usage of osmosis when writing changes to osm api db
On Fri, Dec 10, 2010 at 1:18 AM, Dmytro Korochkin wrote: > Hi all > > I'd like to create the local copy of osm api db. > First I populated DB with full planet.osm file using osmosis, > afterwards initialized and created osm change file. > > Should I run --simplify-change before applying the change file to the db? > > I.e. is it required > nice gzip -d -c change.osm.gz | nice ./osmosis --read-xml-change > file=/dev/stdin --simplify-change --write-xml-change file=- | nice > gzip -9 -c > change.unique.osm.gz > You shouldn't need to use --simplify-change. The api db is made to support full history so the --write-apidb-change task supports writing multiple versions of a single entity to the database. If your only aim it to ensure the api db is fully up to date and you don't care too much about history then --simplify-change might make the processing a little bit faster. Brett ___ osmosis-dev mailing list osmosis-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/osmosis-dev
