Re: [osmosis-dev] Error on a node modified and deleted in the same changeset

2013-05-03 Thread Michael Spreng
On 03.05.2013 23:55, Jocelyn Jaubert wrote: > Do you mean that on diff generated on planet.osm.org, the version on > deleted objects is increased by one ? Not on diff generation, actually, but on the api-db level already, when someone deletes something. I don't know exactly how diffs from the api

Re: [osmosis-dev] bug in read simple task, integer overflow

2013-05-03 Thread Martin Schafran
> Perhaps - is there any specific reason you need to use simple instead > of snapshot? i want to have the option left open to use hibernate. as far as i know hibernate doesn't support hstore. with custom types I could only read the key=>values. ___ os

Re: [osmosis-dev] bug in read simple task, integer overflow

2013-05-03 Thread Martijn van Exel
Perhaps - is there any specific reason you need to use simple instead of snapshot? On Fri, May 3, 2013 at 4:04 PM, Martin Schafran wrote: > I have the newest version. > > It's probably forgotten in the --read-pgsimp task. > > > > > ___ > osmosis-dev mai

Re: [osmosis-dev] bug in read simple task, integer overflow

2013-05-03 Thread Martin Schafran
I have the newest version. It's probably forgotten in the --*read- pgsimp* task. ___ osmosis-dev mailing list osmosis-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/osmosis-dev

Re: [osmosis-dev] Error on a node modified and deleted in the same changeset

2013-05-03 Thread Jocelyn Jaubert
Hi, Le 02/05/2013 22:30, Michael Spreng a écrit : > > This problem comes from the diff, when an object is deleted, the Version > is not incremented. But for logical reasons, it should. This > incrementation is missing in osmosis as well as osmconvert, so at the > moment, custom diffs can't be mer

Re: [osmosis-dev] bug in read simple task, integer overflow

2013-05-03 Thread Martijn van Exel
That integer is just on the wrong side of what you can represent in 32 bits. You probably need to upgrade to an osmosis version that supports 64 bit integers, as the ids in OSM space have crossed the 32 bit boundary recently. On Fri, May 3, 2013 at 3:23 PM, Martin Schafran wrote: > hi, > I tried

[osmosis-dev] bug in read simple task, integer overflow

2013-05-03 Thread Martin Schafran
hi, I tried to report integrity osmosis --rs host=localhost database=osm user=postgres password=? validateSchemaVersion=yes allowIncorrectSchemaVersion=no outPipe.0=db --dd inPipe.0=db outPipe.0=dataset --ri inPipe.0=dataset and got this error SEVERE: Thread for task 1-rs failed org.openstr