J.P. Delport wrote: > > "The vpbmaster command created 473 tasks and after 50 hours of > processing created 1.5 million files with a total size of 487GB." > > The input data is around 800GB if I remember OK. > So the 60 days does sound a bit extreme. >
In our case, VPB created about 130 000 tasks... J.P. Delport wrote: > > Are you getting any messages > that vpb is transforming the coordinate system of your files? > > If so you'd probably be better off doing this as a preprocess step using the > gdal tools. I would e.g. convert the ECW's to Geotiff's in the final > projection that you use. > All our files are already in the final projection. J.P. Delport wrote: > > Also, you could try adding overviews to your input data, e.g. > > gdaladdo my.tiff 2 4 8 16 > > It could speed up vpb's loading of the input data. > ECW naturally includes overview as it is a wavelets-based compression. J.P. Delport wrote: > > You could also try add --compressed --npot to the vpb command line. > I cannot see the npot option details here http://www.openscenegraph.org/projects/VirtualPlanetBuilder/wiki/CommandLineOptions, what is it ? Cheers, Luc ------------------ Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=22499#22499 _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
