Return-Path: <tiff-bounces@lists.maptools.org>
X-Original-To: info@awaresystems.be
Delivered-To: info@awaresystems.be
Received: from mx-i.b-one.net (mx-i.one.com [91.198.169.56])
	by mail9.b-one.net (Postfix) with ESMTP id 91C6D400125
	for <info@awaresystems.be>; Fri, 13 Feb 2009 01:14:57 +0100 (CET)
X-Virus-Scanned: by one.com
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 tagged_above=0 required=6 tests=[none]
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4
Received: from lists.maptools.org (lists.maptools.org [65.39.174.144])
	by mx-i.b-one.net (Postfix) with ESMTP id A50838C24
	for <info@awaresystems.be>; Fri, 13 Feb 2009 01:14:54 +0100 (CET)
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
	by lists.maptools.org (Postfix) with ESMTP id EFE9A1D202948;
	Thu, 12 Feb 2009 19:14:09 -0500 (EST)
Received: from sasl.smtp.pobox.com (a-sasl-quonix.sasl.smtp.pobox.com
	[208.72.237.25])
	by lists.maptools.org (Postfix) with ESMTP id DC26B1D2027E6
	for <tiff@lists.maptools.org>; Thu, 12 Feb 2009 19:07:50 -0500 (EST)
Received: from localhost.localdomain (unknown [127.0.0.1])
	by b-sasl-quonix.sasl.smtp.pobox.com (Postfix) with ESMTP id B56AD2B01B;
	Thu, 12 Feb 2009 19:07:48 -0500 (EST)
Received: from [192.168.2.4] (unknown [67.47.28.121]) (using TLSv1 with
	cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate
	requested)
	by b-sasl-quonix.sasl.smtp.pobox.com (Postfix) with ESMTPSA id
	4AE792B018; Thu, 12 Feb 2009 19:07:43 -0500 (EST)
Message-ID: <4994B9CB.6090505@pobox.com>
Date: Thu, 12 Feb 2009 19:07:39 -0500
From: Frank Warmerdam <warmerdam@pobox.com>
User-Agent: Thunderbird 2.0.0.6 (X11/20071022)
MIME-Version: 1.0
To: pwatkins@crawfordtech.com
References: <20090212230655.0EEB140C076@maroon.pobox.com>
In-Reply-To: <20090212230655.0EEB140C076@maroon.pobox.com>
X-Pobox-Relay-ID: 590F3C48-F962-11DD-8E7E-6F7C8D1D4FD0-06493634!a-sasl-quonix.pobox.com
Cc: tiff@lists.maptools.org
Subject: Re: [Tiff] warning and errors
X-BeenThere: tiff@lists.maptools.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TIFF and libtiff discussion <tiff.lists.maptools.org>
List-Unsubscribe: <http://lists.maptools.org/mailman/listinfo/tiff>,
	<mailto:tiff-request@lists.maptools.org?subject=unsubscribe>
List-Archive: <http://lists.maptools.org/mailman/private/tiff>
List-Post: <mailto:tiff@lists.maptools.org>
List-Help: <mailto:tiff-request@lists.maptools.org?subject=help>
List-Subscribe: <http://lists.maptools.org/mailman/listinfo/tiff>,
	<mailto:tiff-request@lists.maptools.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tiff-bounces@lists.maptools.org
Errors-To: tiff-bounces@lists.maptools.org

Philip Watkinson wrote:
> 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).
> 
> 1. 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.

> 2. 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

_______________________________________________
Tiff mailing list: Tiff@lists.maptools.org
http://lists.maptools.org/mailman/listinfo/tiff
http://www.remotesensing.org/libtiff/
