2021.12.08 03:38 "[Tiff] Windows - difference in behavior when large RowsPerStrip is specified while writing Uncompressed vs LZW compressed TIFF file", by Nalini Vishnoi

2021.12.08 17:16 "Re: [Tiff] Windows - difference in behavior when large RowsPerStrip is specified while writing Uncompressed vs LZW compressed TIFF file", by Even Rouault

For what is worth, I've tried Nalini's test code on Linux 64 bit and it works fine for the LZW compression with libtiff master. Not sure if it would be a Windows or 32-bit specific issue.

The fact that rows_per_strip = 1 when reading the uncompressed image is that libtiff has a strip chopping logic enabled by default (unless you pass the "c" flag in the TIFFOpen() flags) that make libtiff expose a single-strip uncompressed file as having rows_per_strip = 1, to avoid readers that use the TIFFReadEncodedStrip() API to have to allocate undecent amount of memory

Even

http://www.spatialys.com
My software is free, but my time generally not.