Akshay, Caching is done independently for each opened dataset, as long as total caching does not exceed GDAL_CACHEMAX.
You can control the size of the cache with the GDAL_CACHEMAX config option, see the following wiki pages http://trac.osgeo.org/gdal/wiki/ConfigOptions http://trac.osgeo.org/gdal/wiki/UserDocs/GdalWarp GDALRasterBand::RasterIO() takes care of caching internally so you don't have to worry about it GDALRasterBand::ReadBlock() is more efficient but also less flexible. See the various ReadBlock/RasterIO/GetLockedBlockRef functions in http://www.gdal.org/classGDALRasterBand.html Perhaps there is a more descriptive reference somewhere? Etienne On Tue, Mar 13, 2012 at 2:11 AM, akshay gupta <[email protected]> wrote: > > Hi all, > > How exactly does caching work in gdal. If I have 2 or more images opened > simultaneously in gdal, does gdal consider the tiles(or scanlines) belonging > to different images separately or does it keeps a common set, can any body > explain how it is done in gdal. > > Thanks and regards, > Akshay > > > _______________________________________________ > gdal-dev mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/gdal-dev _______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev
