I'm pretty sure I've found and fixed the problem. Can you try the new build I've just created? http://bretth.dev.openstreetmap.org/osmosis-build/osmosis-0.37-SNAPSHOT.zip http://bretth.dev.openstreetmap.org/osmosis-build/osmosis-0.37-SNAPSHOT.tgz
I made a fairly significant change on 14th March to improve the completeWays and completeRelations functionality. Unfortunately I broke the case where a --tee task is used and clipIncompleteEntities=true is set on the --bounding-box task. I've fixed it now. The --tee task makes all entities read-only so that multiple threads can act on the same data. Any tasks that wish to modify the entities must be cloned before use. The --bounding-box task was cloning entities but using the original copy anyway. Silly mistake. Fixed now. On Mon, Aug 2, 2010 at 10:26 PM, NopMap <[email protected]> wrote: > > Hi! > > I did some more experiments. The exception occurs in Osmosis 0.35 and 0.36. > Osmosis 0.34 processes the file just fine. > > The file is http://download.geofabrik.de/osm/europe/germany.osm.bz2 > > Command line > bzip2 -d -c germany.osm.bz2 | osmosis --rx /dev/stdin enableDateParsing=no > --tee outputCount > =1 --bounding-polygon file=main.poly clipIncompleteEntities=yes > idTrackerType=BitSet --wx /dev/stdout | gzip -c > test.osm.gz > > bye > Nop > > -- > View this message in context: > http://osmosis-development.959512.n3.nabble.com/Exception-in-Osmosis-0-36-tp1015401p1015780.html > Sent from the Osmosis Development mailing list archive at Nabble.com. > > _______________________________________________ > osmosis-dev mailing list > [email protected] > http://lists.openstreetmap.org/listinfo/osmosis-dev >
_______________________________________________ osmosis-dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/osmosis-dev
