[OSM-dev] Osmosis RuntimeException: Pipeline entities are not sorted

Gerardo Velez egvelez at gscssoftware.com
Fri Apr 29 19:52:33 UTC 2016


 

Hello,

 

I’ve been using osmosis ver 0.44.1 to update my openstreetmap database for
at least a month without any problem, but today trying to process
http://planet.osm.org/replication/day/000/001/325.osc.gz change file I got
the following error:

 

SEVERE: Thread for task 1-read-xml-change failed

org.openstreetmap.osmosis.core.OsmosisRuntimeException: Pipeline entities
are not sorted, pr

evious entity type=Node, id=199245, version=7 current entity type=Node,
id=199245, version=7

.

 

Looking at the changes file content I notice there are several lines with
exactly the same data which I suppose is the problem, like the following
lines:

 

        <node id="199245" lat="59.3317836" lon="18.3465899" version="7"
timestamp="2016-04-28T00:35:16Z" changeset="38938814" uid="505284"
user="Fringillus">

                <tag k="highway" v="priority"/>

        </node>

        <node id="199245" lat="59.3317836" lon="18.3465899" version="7"
timestamp="2016-04-28T00:35:16Z" changeset="38938814" uid="505284"
user="Fringillus">

                <tag k="highway" v="priority"/>

        </node>

 

What I did just to test was deleting the first one and reprocess the file,
the first error went away but I got the same error for other nodes so I
believe the duplicate data is the problem, as it was working perfect for a
time until today I guess the problem is in the changes file but it would
also be good if osmosis could handle this kind of issues, or if it already
handle them I’d appreciate some hints to remove all duplicate nodes and
process this change file. 

 

Thanks in advance for your help.  

 

Gerardo Vélez

 

 

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/dev/attachments/20160429/00f975f5/attachment.html>


More information about the dev mailing list