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

[IbrahimB22]

Alright, getting closer,

When I run the command you suggested (tried it with the 2-steps method
first, then with the method in one step; the 2-step methode creates the new
osm file, but both methodes crash because of an outOfMemoryException)
I then tried running it like this:

C:\osmosis-0.31.1\bin>java -Xmx1024m -jar "C:\osmosis-0.31.1\osmosis.jar"
--read-xml file="belgium.osm" --bb left="4.6313" top="50.914" right="4.7762"
bottom="50.8416" clipIncompleteEntities=true idTrackerType=BitSet
--write-xml leuven.osm

which outputs this:

25-jul-2009 14:27:02 org.openstreetmap.osmosis.core.Osmosis run
INFO: Osmosis Version 0.31.1
25-jul-2009 14:27:02 org.openstreetmap.osmosis.core.Osmosis main
SEVERE: Execution aborted.
java.lang.NoClassDefFoundError: org/java/plugin/PluginLifecycleException
        at org.openstreetmap.osmosis.core.Osmosis.run(Osmosis.java:73)
        at org.openstreetmap.osmosis.core.Osmosis.main(Osmosis.java:30)
Caused by: java.lang.ClassNotFoundException:
org.java.plugin.PluginLifecycleException
        at java.net.URLClassLoader$1.run(Unknown Source)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(Unknown Source)
        at java.lang.ClassLoader.loadClass(Unknown Source)
        at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
        at java.lang.ClassLoader.loadClass(Unknown Source)
        at java.lang.ClassLoader.loadClassInternal(Unknown Source)
        ... 2 more




Brett Henderson wrote:
> 
> 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.
>>   
> 
> 
> _______________________________________________
> 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-tp24630512p24657538.html
Sent from the OpenStreetMap - Dev mailing list archive at Nabble.com.