> There was a specific, and unrelated, problem this morning that I have
> addressed. Is that what you are referring to?
I'm not sure what the problem was and what was fixed. But I think what
Gerd meant is that changeset uploads in JOSM seem to be slower than
usual. From the opening of the changese
On 12/05/16 22:07, nebulon42 wrote:
There was a specific, and unrelated, problem this morning that I have
addressed. Is that what you are referring to?
I'm not sure what the problem was and what was fixed. But I think what
Gerd meant is that changeset uploads in JOSM seem to be slower than
usua
On 12.05.2016 23:07, nebulon42 wrote:
There was a specific, and unrelated, problem this morning that I have
addressed. Is that what you are referring to?
I'm not sure what the problem was and what was fixed. But I think what
Gerd meant is that changeset uploads in JOSM seem to be slower than
usu
Hi Brett
I tried with --sort-change, but had the same result.
It looks like I need to re-import the full planet again and then go on with
daily updates - I just hope the error does not get propagated further along in
the daily-diffs.
many thanks for your investigation!
Michael
> On 12.05.2016
Actually, on closer inspection of the error it looks like the same node
(257882) is appearing twice with the same version. I doubt if sorting will
help. I don't think Osmosis has a way to fix this issue. The simplify
change task could probably cope with it, but the input validation may be
too st
Okay, so the --simplify-change task is failing because it requires sorted
input.
Can you try this? It will sort the changes before attempting to simplify
them.
osmosis —read-replication-interval workingDirectory=/import/data/diffs/
*--sort-change* --simplify-change --write-xml-change
/import/data
Hi Brett
Sure, here is my stack trace:
May 11, 2016 1:34:36 PM org.openstreetmap.osmosis.core.Osmosis run
INFO: Osmosis Version 0.44.1
May 11, 2016 1:34:36 PM org.openstreetmap.osmosis.core.Osmosis run
INFO: Preparing pipeline.
May 11, 2016 1:34:36 PM org.openstreetmap.osmosis.core.Osmosis run
IN
On 12/05/16 09:48, Gerd Petermann wrote:
it seems that this hardware change has slowed down the update performance,
means, all my updates via JOSM took much longer until the changeset was
closed.
There was a specific, and unrelated, problem this morning that I have
addressed. Is that what you
Hi Grant,
it seems that this hardware change has slowed down the update performance,
means, all my updates via JOSM took much longer until the changeset was
closed.
Is that intended?
Gerd
Grant Slater wrote
> Hi All,
>
> On the 9th of May 2016 the primary OpenStreetMap database will be
> rea
9 matches
Mail list logo
