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

[Brett Henderson]

The bounding box task needs to be inserted into the middle of the 
pipeline (ie. in between the xml read and the pgsql write), so something 
like:

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


You could also do it as a two step process by creating an intermediate 
file like:

osmosis --read-xml file="belgium.osm" --bb left="4.6313" top="50.914" right="4.7762" bottom="50.8416" clipIncompleteEntities=true idTrackerType=BitSet --write-xml mycity.osm

osmosis --read-xml mycity.osm --write-pgsql host="127.0.0.1:5432" database="Routing" user="postgres" password="********" enableLinestringBuilder="yes" nodeLocationStoreType="TempFile"


Both approaches should be fast, but the second one lets you verify the 
specific city data before attempting to load it into postgres.

Brett


IbrahimB22 wrote:
> 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.
>