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

[Jocelyn Jaubert]

Hi,

I have just switched to Geofabrik's diffs to update my Switzerland .pbf file, and I'm hitting an issue with diffs. I'm not quite sure if the issue is with osmosis or not.

When downloading these two files:

http://download.geofabrik.de/europe/switzerland-updates/000/000/058.osc.gz
http://download.geofabrik.de/europe/switzerland-updates/000/000/059.osc.gz

and merging them through --read-replication-interval

You will see that node 559647562 is present twice, with the same changeset:

<?xml version='1.0' encoding='UTF-8'?>
<osmChange version="0.6" generator="Osmosis 0.41">
  <modify>
    <node id="559647562" version="2" timestamp="2013-04-29T12:55:06Z" uid="65044" user="hugi" changeset="15907651" lat="46.9473255" lon="7.4651306"/>
  </modify>
  <delete>
    <node id="559647562" version="2" timestamp="2013-05-01T00:33:27Z" uid="65044" user="hugi" changeset="15907651" lat="46.9473255" lon="7.4651306"/>
  </delete>
</osmChange>

So first question: should this be correctly handled by osmosis ? Currently, a --sort-change complains about a non-sorted file:

GRAVE: Thread for task 1-read-xml-change failed
org.openstreetmap.osmosis.core.OsmosisRuntimeException: Pipeline entities are not sorted, previous entity type=Node, id=559647562, version=2 current entity type=Node, id=559647562, version=2.



According to this node history:

http://www.openstreetmap.org/browse/node/559647562/history

this node was in fact deleted in a following changeset

Could there be an issue with how the diffs are generated ?


Thanks,
Jocelyn