Hi Frederik, Thanks for the quick reply!
As you suspected, the temporary file was the issue. Java defaults to using the /tmp partition as a space for creating temporary files, and in my case I only have 16MB of disk space available there! In order to correct the problem, I pointed Java to a temporary space on my main (950GB) partition by setting the JAVACMD_OPTIONS appropriately: JAVACMD_OPTIONS="-Djava.io.tmpdir=/home/james/tmp" osmosis (...) Now it runs without crashing. Thank you so much for your help, and the suggested workaround! Best Regards, James On Fri, Sep 11, 2009 at 4:42 AM, Frederik Ramm <[email protected]> wrote: > Hi, > > James P. Biagioni wrote: >> >> When I try to cut a bounding box out of the Planet.osm file, with the >> completeWays=yes option on, I receive the error: java.io.IOException: >> No space left on device > > This option creates a large (10s of GB) temporary file. Is it possible that > the temporary file is created on another disk partition where you do not > have so much space? > > The size of the temp file is proportional to the size of the input file. So > if you e.g. cut a little area out of the full planet, you will have a > full-size temporary file. In such a situation performance will improve > dramatically if you first cut out a slighty larger area than required > WITHOUT completeWays=yes, and only then cut out the smaller area - in this > case only the stuff you cut out first needs to go to the temp file: > > osmosis --rx planet.osm --bb <larger_bounding_box> > clipIncompleteEntities=yes --bb <smaller_bounding_box> completeWays=Yes --wx > cutout.osm > > Of course this will lose any nodes which are outside of the larger bbox. > > Bye > Frederik > > _______________________________________________ osmosis-dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/osmosis-dev
