[gdal-dev] GTiff optimisation

[Matt Wilkie]

Yves,  it's best to use gdalwarp without any compression options and 
then use gdal_translate as a last step to apply the compression. See 
http://trac.osgeo.org/gdal/wiki/UserDocs/GdalWarp#GeoTIFFoutput-coCOMPRESSisbroken 
for more.

cheers,

matt wilkie
--------------------------------------------
Geomatics Analyst
Information Management and Technology
Yukon Department of Environment
10 Burns Road * Whitehorse, Yukon * Y1A 4Y9
867-667-8133 Tel * 867-393-7003 Fax
http://environmentyukon.gov.yk.ca/geomatics/
--------------------------------------------


On 30/08/2011 4:22 AM, Yves Jacolin wrote:
> Hello,
>
> I am converting GTiff to GTiff in order to add projection and georeferencing
> information in the header. I am using gdalwarp with some flags, mailny -co
> flags. I have some question about this.
>
> Here is my command line:
>
> gdalwarp -co "COMPRESS=PACKBITS" -co "PHOTOMETRIC=MINISWHITE" -co "NBITS=1" -
> s_srs "EPSG:2154" -t_srs "EPSG:2154" input.tif output.tif
>
> 1.  File size: input.tif and output.tif have different file size, output file is
> 50 % bigger than the input file. Is it normal?
>
> 2. If I use gdalinfo on my output file, I have no information about MINISWHITE
> parameter while I have it in the input file. Am I using this creation option
> correctly? This issue could be related to the first item?
>
> 3. I also have a "AREA_OR_POINT=Area" item in my output from gdalinfo, what
> does it means?
>
> gdal version: GDAL 1.7.3, released 2010/11/10
>
> thanks,
>
> Y.