Return-Path: <tiff-bounces@lists.maptools.org>
Received: from inas032.isp.belgacom.be (localhost [127.0.0.1])
        by inav029.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-IN-AV-3.00) with ESMTP id kA1GHqVB010358
        for <joris.at.lebbeke@skynet.be>; Wed, 1 Nov 2006 17:17:52 +0100
        (envelope-from <tiff-bounces@lists.maptools.org>)
Received: from inmx012.isp.belgacom.be (inmx012.isp.belgacom.be [195.238.5.90])
	by inas032.isp.belgacom.be (Postfix) with ESMTP id C6AD23A0066
	for <joris.at.lebbeke@skynet.be>; Wed,  1 Nov 2006 17:17:52 +0100 (CET)
Received: from duke.maptools.org (r153.dmsolutions.ca [209.217.116.153] (may be forged))
        by inmx012.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-IN-2.32) with ESMTP id kA1GHiEk026106
        for <joris.at.lebbeke@skynet.be>; Wed, 1 Nov 2006 17:17:44 +0100
        (envelope-from <tiff-bounces@lists.maptools.org>)
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 kA1GA8Hv026712;
	Wed, 1 Nov 2006 11:10:17 -0500
Received: from scmze001.ssan.egs-seg.gc.ca (scmze001.ssan.egs-seg.gc.ca
	[205.194.19.85])
	by duke.maptools.org (8.12.11/8.12.10) with ESMTP id kA1GA4eP026709
	for <tiff@lists.maptools.org>; Wed, 1 Nov 2006 11:10:05 -0500
Received: from bulwark1.ic.gc.ca ([192.197.178.1])
	by scmze001.ssan.egs-seg.gc.ca with ESMTP; 01 Nov 2006 11:02:14 -0500
Received: from msg-gate1.ic.gc.ca ([142.53.11.41]) by bulwark1.ic.gc.ca
	via smtpd (for scmze001.ssan.egs-seg.gc.ca [205.194.19.85]) with ESMTP;
	Wed, 1 Nov 2006 11:02:14 -0500
Received: from parapet11.ic.gc.ca (parapet11.ic.gc.ca [142.53.11.253])
	by msg-gate1.ic.gc.ca (Switch-3.1.8/Switch-3.1.7) with ESMTP id
	kA1G2E5Z021373
	for <tiff@lists.maptools.org>; Wed, 1 Nov 2006 11:02:14 -0500 (EST)
Received: from msg-con2.icent.ic.gc.ca by parapet11.ic.gc.ca
	via smtpd (for msg-gate1.ic.gc.ca [142.53.11.41]) with ESMTP;
	Wed, 1 Nov 2006 11:02:14 -0500
Received: from msg-con1.icent.ic.gc.ca ([142.53.28.148]) by
	msg-con2.icent.ic.gc.ca with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 1 Nov 2006 11:02:14 -0500
Received: from msg-mb2.icent.ic.gc.ca ([142.53.28.151]) by
	msg-con1.icent.ic.gc.ca with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 1 Nov 2006 11:02:13 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Tiff] splitting G4 image without decompression
Date: Wed, 1 Nov 2006 11:02:13 -0500
Message-ID: <F78E6BBD22A6FC4489EBE2504540790805592643@msg-mb2.icent.ic.gc.ca>
In-Reply-To: <20061101154752.80911.qmail@web53112.mail.yahoo.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Tiff] splitting G4 image without decompression
Thread-Index: Acb9zhGAiK3J1tl1Rua3tO9WschUHwAADYAw
From: "Pallek, Bernie: #CIPO - OPIC" <Pallek.Bernie@ic.gc.ca>
To: <tiff@lists.maptools.org>
X-OriginalArrivalTime: 01 Nov 2006 16:02:13.0983 (UTC)
	FILETIME=[189FEEF0:01C6FDCF]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by duke.maptools.org id
	kA1GA4eP026709
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
X-UIDL: 000000000023ceae.00001cf6
X-MSP-STORE: Wed, 01 Nov 2006 17:17:58 +0100
Status:   

Marvin wrote:
> Is it possible to split a G4 image into several G4
> subimages without decompressing?

Probably not.  The vertical (2D) compression scheme relies on a previous line (an imaginary white line in the case of the first), so even if you could break the compressed data block into sub-blocks at line boundaries (already difficult/impossible), only the first sub-block would be able to use the imaginary white line above the image; the rest of the sub-blocks would be depending on the last line of the previous sub-block, which wouldn't be handled well by the standard decompression algorithm.

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