-
2009.02.12 22:53 "Re: [Tiff] warning and errors", by Frank Warmerdam
-
2009.02.12 23:06 "Re: [Tiff] warning and errors", by Philip Watkinson
- 2009.02.12 23:56 "Re: [Tiff] warning and errors", by Bob Friesenhahn
- 2009.02.13 00:07 "Re: [Tiff] warning and errors", by Frank Warmerdam
- 2009.02.13 08:34 "Re: [Tiff] warning and errors", by
- 2009.02.19 17:17 "[Tiff] Bug in tiff_jpeg.c dealing with pre-subsampled ycbcr data passed to TIFFWriteEncodedXxx", by
-
2009.02.12 23:06 "Re: [Tiff] warning and errors", by Philip Watkinson
2009.02.13 00:07 "Re: [Tiff] warning and errors", by Frank Warmerdam
We want to use Libtiff in a production evironment. We don't want warnings/error messages unless there is a critical error (the image is corrupt).
- Is there a listing of warnings which indicate that the image is corrupt?
Philip,
I'm not aware of such a list, and corrupt can mean different things to different people.
- If Libtiff generates an error, can I assume it is a critical error?
It depends on what you mean by critical. For instance, libtiff might report an error when reading one strip/tile of an image, but it might still be fruitful to continue trying to read other strips.
But, in general, if you get an error from libtiff it is likely the image is not going to be recovered properly. In general, things will likely work ok if you supress all warnings.
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