Thanks for that Vincent, very interesting.
Vincent Schut-2 wrote: > > > In case someone is interested, personally I use these optimization rules: > - random write access: don't compress, strip or tile and pixel or band > interleave according to read/write algorithm; > - mainly intended for reading/viewing: don't compress, square tiles > (256x256), add pyramids; > - intended for clients that use commercial GIS/RS software: pixel > interleave, strip oriented, no compression, no strange data types > - space is really really really an issue and I am sure I don't need any > random write access to it and I am the only one that wants to read/view > it: band interleaved, usually tiled, deflate compression. Sometimes add > (compressed) pyramids. > > Cheers, > Vincent. >> -- View this message in context: http://www.nabble.com/Tif-file-getting-larger-and-larger-tp18976082p18992723.html Sent from the GDAL - Dev mailing list archive at Nabble.com. _______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev
