Received: from mailgate011.isp.belgacom.be (mailgate011.isp.belgacom.be [195.238.6.4])
	by maildelivery011.isp.belgacom.be (Postfix) with ESMTP id A4612598003
	for <joris.at.lebbeke@skynet.be>; Thu, 10 Jan 2008 23:01:06 +0100 (CET)
Authentication-Results: in.mx.skynet.be header.from=shirahatti@gmail.com; dkim=permfail (body hash did not verify [TEST])
Received: from r153.dmsolutions.ca (HELO duke.maptools.org) ([209.217.116.153])
  by in.mx.skynet.be with ESMTP; 10 Jan 2008 23:01:05 +0100
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 m0ALeL1B008567;
	Thu, 10 Jan 2008 16:40:34 -0500
Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.234])
	by duke.maptools.org (8.12.11/8.12.10) with ESMTP id m0ALeIFT008564
	for <tiff@lists.maptools.org>; Thu, 10 Jan 2008 16:40:18 -0500
Received: by nz-out-0506.google.com with SMTP id z6so491835nzd.9
	for <tiff@lists.maptools.org>; Thu, 10 Jan 2008 13:40:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references;
	bh=LbfJisYWe+sqQYdDdwxaP4wTUzQHh3mjzaWV0srNgWI=;
	b=dpCy7SfBAiQ0HOxLMd/q9NiXtbwOIZaihD0PGxDAnes4fVoogCFBU8h2JLFmpvdG9TeEyl/HAk6bSYbZXmBBhDkskLdpqnEf03vmY3LtHe8ha0iIToq1II5P1lazQGMSnLgGUxg4kPpMWomkeyu8bHwDzFB+68IcXFknoQeyquU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references;
	b=s/DKv28M80YFEKyurVNhzfMIsOKhI65eaq+hWjDKUgk/EZ3D988OEOwq7wvIDfPWdD+8pcx1T5ZD/JS0lLGlHbSMNEt0esXyQ1lSwHP3fmYeTzoHCK0hFHwETVW4clkmPy38SZRmi7QXY3bidBfXiIINUddAlw+wPwxZsVcIkPw=
Received: by 10.141.18.14 with SMTP id v14mr1514919rvi.252.1200001215933;
	Thu, 10 Jan 2008 13:40:15 -0800 (PST)
Received: by 10.140.191.7 with HTTP; Thu, 10 Jan 2008 13:40:15 -0800 (PST)
Message-ID: <fb91ffe0801101340g1ea9c156h11b53e0d1aa7a03e@mail.gmail.com>
Date: Thu, 10 Jan 2008 13:40:15 -0800
From: "Nikhil Shirahatti" <shirahatti@gmail.com>
To: "Bob Friesenhahn" <bfriesen@simple.dallas.tx.us>
Subject: Re: [Tiff] LibTiff..Reading partial strips
In-Reply-To: <Pine.SOC.4.64.0801101531190.2557@freddy.simplesystems.org>
MIME-Version: 1.0
References: <fb91ffe0801101103o3addbc5bhd6fb7234fbef1216@mail.gmail.com>
	<Pine.SOC.4.64.0801101531190.2557@freddy.simplesystems.org>
Cc: tiff@lists.maptools.org
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>
Content-Type: multipart/mixed; boundary="===============0674006386=="
Sender: tiff-bounces@lists.maptools.org
Errors-To: tiff-bounces@lists.maptools.org
X-UIDL: 000000000023ceae.000029d2
X-MSP-STORE: Thu, 10 Jan 2008 23:01:06 +0100
Status:   

--===============0674006386==
Content-Type: multipart/alternative; 
	boundary="----=_Part_8844_18792335.1200001215933"

------=_Part_8844_18792335.1200001215933
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I havent tried it..but the cautionary note that " It is not always possible
to do so due to decompression constraints" scares me. I also read on the
archive that "that *strip* *chopping* only works for uncompressed  IFDs.".
How common(or uncommon) is this? When would one use compressed IFD's?
 The tiff's we get can be compressed or uncompressed formats and we have to
support them all. :)

Nikhil

On Jan 10, 2008 1:33 PM, Bob Friesenhahn <bfriesen@simple.dallas.tx.us>
wrote:

> On Thu, 10 Jan 2008, Nikhil Shirahatti wrote:
> >
> > This is the problem I' trying to solve:
> > to read a strip but not a whole strip but only part of it...reason: some
> of
>
> I believe that libtiff has a strip-chopping build option.  This may be
> in the build defaults.  The strip-chopping option should break long
> strips into multiple small strips/scanlines if possible.  It is not
> always possible to do so due to decompression constraints.  Does this
> feature not work for you?
>
> Bob
> ======================================
> Bob Friesenhahn
> bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
> GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/
>
>


-- 
-----------------------------------------------------------------
Nikhil V Shirahatti
http://vision.cs.arizona.edu/nvs

------=_Part_8844_18792335.1200001215933
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I havent tried it..but the cautionary note that &quot; It is not always possible to do so due to decompression constraints&quot; scares me. I also read on the archive that &quot;<span>that <b class="highlight">strip</b> <b class="highlight">
chopping</b> only works for uncompressed&nbsp; 
</span><span>IFDs.&quot;. How common(or uncommon) is this? When would one use compressed IFD&#39;s?<br></span>&nbsp;The tiff&#39;s we get can be compressed or uncompressed formats and we have to support them all. :)<br><br>Nikhil
<br><br><div class="gmail_quote">On Jan 10, 2008 1:33 PM, Bob Friesenhahn &lt;<a href="mailto:bfriesen@simple.dallas.tx.us">bfriesen@simple.dallas.tx.us</a>&gt; wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Thu, 10 Jan 2008, Nikhil Shirahatti wrote:<br>&gt;<br>&gt; This is the problem I&#39; trying to solve:<br>&gt; to read a strip but not a whole strip but only part of it...reason: some of<br><br></div>
I believe that libtiff has a strip-chopping build option. &nbsp;This may be<br>in the build defaults. &nbsp;The strip-chopping option should break long<br>strips into multiple small strips/scanlines if possible. &nbsp;It is not<br>always possible to do so due to decompression constraints. &nbsp;Does this
<br>feature not work for you?<br><br>Bob<br>======================================<br><font color="#888888">Bob Friesenhahn<br><a href="mailto:bfriesen@simple.dallas.tx.us">bfriesen@simple.dallas.tx.us</a>, <a href="http://www.simplesystems.org/users/bfriesen/" target="_blank">
http://www.simplesystems.org/users/bfriesen/</a><br>GraphicsMagick Maintainer, &nbsp; &nbsp;<a href="http://www.GraphicsMagick.org/" target="_blank">http://www.GraphicsMagick.org/</a><br><br></font></blockquote></div><br><br clear="all">
<br>-- <br>-----------------------------------------------------------------<br>Nikhil V Shirahatti<br><a href="http://vision.cs.arizona.edu/nvs">http://vision.cs.arizona.edu/nvs</a>

------=_Part_8844_18792335.1200001215933--

--===============0674006386==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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