To save size and disk i/o you can also use a vrt intermediate file
gdalwarp -of vrt -r bilinear infile ofile.vrt
gdal_translate -co "COMPRESS=PACKBITS" ofile.vrt ofile.tif
rm ofile.vrt
On Thu, Sep 13, 2012 at 12:57 PM, Eli Adam wrote:
> Rutger,
>
> There are some notes on this on the wiki too,
Rutger,
There are some notes on this on the wiki too,
http://trac.osgeo.org/gdal/wiki/UserDocs/GdalWarp#GeoTIFFoutput-coCOMPRESSisbroken
Regards, Eli
On Thu, Sep 13, 2012 at 8:16 AM, Rutger wrote:
> Thanks for the tip, i wasn't aware of the -wo flags. Im testing it right now,
> but at 20% its a
Thanks for the tip, i wasn't aware of the -wo flags. Im testing it right now,
but at 20% its already taking 20 minutes, so its certainly not very
practical, but im curious of the result.
For comparison, the earlier mentioned gdalwarp operation takes 72 seconds,
running gdal_translate after it tak
Le 2012-09-13 16:28, Rutger a écrit :
Dear list,
Im using the gdalwarp command-line utility on Windows and im running
into
some strange behavior. When reprojecting a large global grid to a
subset,
the output filesize is way too large. Its a lot larger than
xsize*ysize*datatype, and when pulli
Dear list,
Im using the gdalwarp command-line utility on Windows and im running into
some strange behavior. When reprojecting a large global grid to a subset,
the output filesize is way too large. Its a lot larger than
xsize*ysize*datatype, and when pulling the file through gdal_translate
shrinks
Hey,
thanks a lot for the patch. Now I can use my ECW rastafiles again and finish
my job. I searched for many weeks but very late the idea to contact the
gdal-dev mailinglist came to my mind. I willspread the solution because I
remeber some threads according this problem.
thanks
Fabian
--
Vie
