[OSM-dev] Osmosis shutting down while processing osm-file

[IbrahimB22]

Hi,

I tried the workaround with the bounding box, but with no success.

osmosis --read-xml file="belgium.osm" --write-pgsql host="127.0.0.1:5432"
database="Routing" user="postgres" password="********"
enableLinestringBuilder="yes" nodeLocationStoreType="TempFile" --bb
left="4.6313" top="50.914" right="4.7762" bottom="50.8416"
clipIncompleteEntities=true idTrackerType=BitSet

I tried to extract a specific city from the belgium.osm, I guess that would
be the same principle as extracting belgium from the planet file.

The output I'm getting:

25-jul-2009 13:23:02 org.openstreetmap.osmosis.core.Osmosis run
INFO: Osmosis Version 0.31.1
25-jul-2009 13:23:02 org.openstreetmap.osmosis.core.Osmosis run
INFO: Preparing pipeline.
25-jul-2009 13:23:02 org.openstreetmap.osmosis.core.Osmosis main
SEVERE: Execution aborted.
org.openstreetmap.osmosis.core.OsmosisRuntimeException: No default pipes are
available as input for task 3-bb.
        at
org.openstreetmap.osmosis.core.pipeline.common.PipeTasks.retrieveTask(PipeTasks.java:150)
        at
org.openstreetmap.osmosis.core.pipeline.common.TaskManager.getInputTask(TaskManager.java:165)
        at
org.openstreetmap.osmosis.core.pipeline.v0_6.SinkSourceManager.connect(SinkSourceManager.java:51)
        at
org.openstreetmap.osmosis.core.pipeline.common.Pipeline.connectTasks(Pipeline.java:74)
        at
org.openstreetmap.osmosis.core.pipeline.common.Pipeline.prepare(Pipeline.java:116)
        at org.openstreetmap.osmosis.core.Osmosis.run(Osmosis.java:79)
        at org.openstreetmap.osmosis.core.Osmosis.main(Osmosis.java:30)

Kind Regards,

Ibrahim


Brett Henderson wrote:
> 
> Hi Ibrahim,
> 
> This sounds like the same problem encountered by Torge Szczepanek on 
> 21st July at 23:37 (UTC).  I've included the message I wrote to him at 
> the time.
> 
> Let us know if this is a suitable workaround to the problem.
> 
> Brett
> 
> 
> Hi Torge,
> 
> I haven't seen this particular error before.  My suspicion is that it's 
> caused by ways referring to non-existent nodes.  I thought the code was 
> capable of dealing with that scenario, but it looks like that isn't the 
> case.
> 
> I don't have time to look into this at the moment, but one workaround 
> might be to run the entire planet through the --bbox task:
> --bbox clipIncompleteEntities=true idTrackerType=BitSet
> 
> The --bbox task as specified above will modify ways to ensure 
> referential integrity.
> 
> I hope that helps.
> 
> Brett
> 
> _______________________________________________
> dev mailing list
> dev at openstreetmap.org
> http://lists.openstreetmap.org/listinfo/dev
> 
> 

-- 
View this message in context: http://www.nabble.com/Osmosis-shutting-down-while-processing-osm-file-tp24630512p24657185.html
Sent from the OpenStreetMap - Dev mailing list archive at Nabble.com.