Hi Simon, The duplicate node entry could be caused by a couple of reasons:
1. There were bugs in some builds of Osmosis 0.31.1. Is there a reason you're using 0.31.1? The latest stable version is 0.32. You can get it here: http://wiki.openstreetmap.org/index.php/Osmosis#Latest_Stable_Version 2. Are you using replication diffs instead of daily diffs? These diffs can contain multiple version of the same entity because they are full history diffs. The delta style daily diffs are more appropriate for patching osm files. Brett On Sun, Jan 10, 2010 at 7:54 PM, Simon Nuttall <[email protected]>wrote: > It was suggested that I try to sort the nodes first, so I tried that using: > > osmosis -v 100 --read-xml data/osm/downloads/great_britain.osm > enableDateParsing=no --bounding-polygon file="import/fz_cambridge.txt" > --sort-0.6 --write-xml data/osm/downloads/great_britain.sorted.osm > > but it made no difference to the order of the appearance of these two > nodes: > > <node id="620823" version="9" timestamp="2010-01-10T00:42:28Z" > uid="215789" user="smncrsk" changeset="3560454" lat="52.1920125" > lon="0.1884885"/> > <node id="620823" version="10" timestamp="2010-01-10T00:42:28Z" > uid="215789" user="smncrsk" changeset="3564864" lat="52.191996" > lon="0.1884762"/> > > which seem to be causing the problem, with the same error report > previously reported: > > SEVERE: Thread for task 1-read-xml failed > org.openstreetmap.osmosis.core.OsmosisRuntimeException: Pipeline > entities are not sorted, previous entity type=Node, id=620823, > version=9 current entity type=Node, id=620823, version=10. > at > org.openstreetmap.osmosis.core.merge.v0_6.impl.SortedEntityPipeValidator.process(SortedEntityPipeValidator.java:47) > > Simon >
_______________________________________________ osmosis-dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/osmosis-dev
