I've fixed that one in svn. Not many have run into it. From changes.txt: * Fixed a bug in --bounding-box and --bounding-polygon preventing use of clipIncompleteEntities after a --tee task.
It's due to a tee task marking entities as read-only to avoid multiple threads modifying entities at the same time. But the clipIncompleteEntities option was attempting to modify them, I've fixed it to get a writeable copy of entities before modifying them. Hmm, you're doing a great job of finding flaws in Osmosis today :-) I'm not sure what the right answer is here, I guess your only option is to use the latest snapshot. I need to push out a 0.37 release, but have been holding off until the binary tasks are ready. Brett On Mon, Sep 13, 2010 at 4:50 PM, Frederik Ramm <[email protected]> wrote: > Hi, > > moving this from dev to osmosis-dev: > > Frederik Ramm wrote: > >> 0.36 seems to work. Anything prior, probably not. Then again hardly anyone >> uses the hourlies I guess. >> > > I'm seeing another problem, after upgrading to 0.36. It's not related to > the diffs any more, these are fine; but my job that cuts out continents and > worked fine with 0.32: > > osmosis > --fast-read-xml-0.6 current-planet.osm > --buffer --tee 6 > --bp file=africa.poly clipIncompleteEntities=true idTrackerType=BitSet > --write-xml-0.6 africa.osm > --bp file=asia.poly clipIncompleteEntities=true idTrackerType=BitSet > --write-xml-0.6 asia.osm > --bp file=australia-oceania.poly clipIncompleteEntities=true > idTrackerType=BitSet --write-xml-0.6 australia-oceania.osm > --bp file=central-america.poly clipIncompleteEntities=true > idTrackerType=BitSet --write-xml-0.6 central-america.osm > --bp file=europe.poly clipIncompleteEntities=true > idTrackerType=BitSet --write-xml-0.6 europe.osm > --bp file=south-america.poly clipIncompleteEntities=true > idTrackerType=BitSet --write-xml-0.6 south-america.osm > > now results in the following error: > > SEVERE: Thread for task 2-buffer failed > java.lang.UnsupportedOperationException > at > java.util.Collections$UnmodifiableCollection$1.remove(Collections.java:1028) > at > org.openstreetmap.osmosis.areafilter.v0_6.AreaFilter.emitWay(AreaFilter.java:277) > at > org.openstreetmap.osmosis.areafilter.v0_6.AreaFilter.process(AreaFilter.java:191) > at > org.openstreetmap.osmosis.core.container.v0_6.WayContainer.process(WayContainer.java:60) > at > org.openstreetmap.osmosis.areafilter.v0_6.AreaFilter.process(AreaFilter.java:104) > at > org.openstreetmap.osmosis.core.tee.v0_6.EntityTee$ProxySinkSource.process(EntityTee.java:124) > at > org.openstreetmap.osmosis.core.tee.v0_6.EntityTee.process(EntityTee.java:70) > at > org.openstreetmap.osmosis.core.buffer.v0_6.EntityBuffer.run(EntityBuffer.java:74) > at java.lang.Thread.run(Thread.java:636) > > I'll debug this further - currently unsure if there's something wrong with > the input data or what. The problem occurs about 1h50m hours into processing > the job. so it looks more like it is towards the end. > > Bye > Frederik >
_______________________________________________ osmosis-dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/osmosis-dev
