[gdal-dev] Bigger file size from 64-bit than 32-bit

Jukka Rahkonen jukka.rahkonen at mmmtike.fi
Thu Jan 16 06:42:49 PST 2014

Even Rouault <even.rouault <at> mines-paris.org> writes:

> --> ouch ! I fail to see any reason why the on-disk format would be
affected by
> 32 vs 64 bit. You could run "tiffdump" on the generated images to see the
> and size of the tiles. What is surprising is that the 32 bit JPEG TIF is
> than the original JP2. Does it display correctly ?
> Does gdalinfo -checksum return the same values ?

Ok, the images in this B/W set converted with 64-bit binaries are not only
big but they are totally broken. I will need to check the B/W images I have
processed so far with these binaries and see if they are all broken. I know
that colour images are good and I believe that I have also checked a bunch
of B/W images. This certain B/W batch is compressed into JPEG2000 a long
time ago with another program and settings than I use nowadays so it can be
that other images are not affected. I will tell more after doing some

Originals are compressed as lossless JPEG2000 so it is normal that a jpeg
compressed tiff is much smaller.

> >
> > Builds I use are specially made by Tamas and I can ask for details if
> > someone gives a hint about what to ask.
> --> Do you mean custom builds, and not the standard ones available on
> gisinternals ? If they are custom, do you reproduce with the standard ones ?

Yes, a custom build with Kakadu v. 7.3.2 plugin. I will do more tests
tomorrow once this batch of 3500 images is converted.


More information about the gdal-dev mailing list