AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2005.11.23 02:32 "[Tiff] libtiff and over 4GB files", by Frank Warmerdam
2005.11.23 02:57 "Re: [Tiff] libtiff and over 4GB files", by Edward Lam
2005.11.23 04:01 "Re: [Tiff] libtiff and over 4GB files", by Frank Warmerdam
2005.11.23 03:24 "Re: [Tiff] libtiff and over 4GB files", by Joris
2005.11.23 04:06 "Re: [Tiff] libtiff and over 4GB files", by Frank Warmerdam
2005.11.23 04:51 "Re: [Tiff] libtiff and over 4GB files", by Bob Friesenhahn
2005.11.23 13:36 "Re: [Tiff] libtiff and over 4GB files", by Frank Warmerdam
2005.11.23 19:55 "Re: [Tiff] libtiff and over 4GB files", by Chris Cox
2006.01.18 05:59 "Re: [Tiff] TIFF formats Libtiff supports", by katrina maramba
2006.01.18 02:15 "[Tiff] TIFF formats Libtiff supports", by katrina maramba
2006.01.18 04:55 "Re: [Tiff] TIFF formats Libtiff supports", by Frank Warmerdam
2006.01.18 12:47 "Re: [Tiff] TIFF formats Libtiff supports", by Frank Warmerdam

2005.11.23 02:32 "[Tiff] libtiff and over 4GB files", by Frank Warmerdam

Folks,

This post is *not* about BigTIFF. Instead it is about how libtiff reports errors if the application attempts to write a file larger than 4GB. The short answer is that libtiff doesn't seem to even notice, it just writes out a corrupt file (with tile/strip offsets wrapping back to 0 at the 4GB mark).

I have created a bug on this issue at:

  http://bugzilla.remotesensing.org/show_bug.cgi?id=1004

I am interested in feedback from folks on appropriate or inappropriate approaches to dealing with this problem. Does anyone depend on libtiff being able to write a bit past the 4GB mark? Does libtiff report errors, and I am just ignoring them somehow?

Best regards,
--

---------------------------------------+--------------------------------------
I set the clouds in motion - turn up   | Frank Warmerdam, warmerdam@pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush    | Geospatial Programmer for Rent