Hermann Peifer wrote:
Frank Warmerdam wrote:
This sounds like a heap of processing that needs to be done.
You can increase the chunk size on which gdal_rasterize operates by
increasing the GDAL_CACHEMAX config option. I would suggest sizing
it to be roughly 1/3 of your machine RAM.
eg.
gdal_rasterize --config GDAL_CACHEMAX 600 ...
would be appropriate on a machine with 2GB of RAM.
Beyond that I can't think of much that might help. The above basically
reduces the number of passes needed through the vector data. It is all
processed once for each chunk of the raster that is processed.
Thanks.
Could the performance be improved by optimizing my blank tif: e.g.
compressed or not, tiled or not?
Hermann,
Uncompressed will help a bit perhaps, but there is only one pass made
over the raster, and in large chunks, so it won't make much difference.
Best regards,
--
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up | Frank Warmerdam, [email protected]
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush | Geospatial Programmer for Rent
_______________________________________________
gdal-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/gdal-dev
