Received: from mailgate010.isp.belgacom.be (mailgate010.isp.belgacom.be [195.238.6.3])
	by maildelivery022.isp.belgacom.be (Postfix) with ESMTP id 991ED1A403E
	for <joris.at.lebbeke@skynet.be>; Wed, 22 Aug 2007 15:19:58 +0200 (CEST)
Received: from r153.dmsolutions.ca (HELO duke.maptools.org) ([209.217.116.153])
  by in.mx.skynet.be with ESMTP; 22 Aug 2007 15:19:56 +0200
Received: from duke.maptools.org (duke.maptools.org [127.0.0.1])
	by duke.maptools.org (8.12.11/8.12.10) with ESMTP id l7MD4epe022583;
	Wed, 22 Aug 2007 09:05:11 -0400
Received: from zynlfw01.zylab.com (mx.zylab.com [194.178.9.130])
	by duke.maptools.org (8.12.11/8.12.10) with ESMTP id l7MD4Ahq022579
	for <tiff@lists.maptools.org>; Wed, 22 Aug 2007 09:04:11 -0400
Received: from zynlms01.ZyLAB.WAN (zynlms01.zylab.wan [192.168.1.10])
	by zynlfw01.zylab.com (Postfix) with ESMTP id 6A920414;
	Wed, 22 Aug 2007 15:04:09 +0200 (CEST)
Content-class: urn:content-classes:message
Subject: Re: [Tiff] How to handle big single-strip images?
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Date: Wed, 22 Aug 2007 15:00:56 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Message-ID: <FC840EC0BF7BFA45A0F94548AF36920D020CA8D0@zynlms01.ZyLAB.WAN>
In-Reply-To: <154EE652-27B3-45EB-B40D-808306F67091@kreisbote.de>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Tiff] How to handle big single-strip images?
Thread-Index: AcfkhjJNg0egQorrSZC3ZioccO4/NAANRZ2Q
References: <154EE652-27B3-45EB-B40D-808306F67091@kreisbote.de>
From: "Gerben Vos" <Gerben@zylab.com>
To: <tiff@lists.maptools.org>
X-MIME-Autoconverted: from quoted-printable to 8bit by duke.maptools.org id
	l7MD4Ahq022579
Cc: 
X-BeenThere: tiff@lists.maptools.org
X-Mailman-Version: 2.1.4
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>
Sender: tiff-bounces@lists.maptools.org
Errors-To: tiff-bounces@lists.maptools.org
Content-Transfer-Encoding: quoted-printable
X-UIDL: 000000000023ceae.0000274d
X-MSP-STORE: Wed, 22 Aug 2007 15:19:58 +0200
Status: RO

Oliver Geisen wrote:

> i wonder what will happen if one opens an tiff image where all the
> data is in a SINGLE strip (some writers offer this option) and also
> compressed (G4) and someone tries to use TIFFReadScanline with it?
> I would expect that libtiff needs to read the whole strip, because
> it's compressed, into memory. Or is it possible to read compressed
> data by chunks?

libtiff can decompress data by chunks that are multiples of a scanline.

This may depend on the compression type, but it's definitely supported
for CCITT, LZW, ZIP and JPEG.

					Gerben Vos.

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