Return-Path: <tiff-bounces@remotesensing.org>
Received: from inmx013.isp.belgacom.be (inmx013.isp.belgacom.be [195.238.2.216])
        by mailst034.isp.belgacom.be (8.12.11/8.12.11/Skynet-MAILSTORE-2.14) with ESMTP id i91EGMkg001788
        for <joris.at.lebbeke@skynet.be>; Fri, 1 Oct 2004 16:16:22 +0200
        (envelope-from <tiff-bounces@remotesensing.org>)
Received: from xserve.flids.com (adsl-065-083-169-202.sip.mco.bellsouth.net [65.83.169.202])
        by inmx013.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-2.32) with ESMTP id i91EGChG012428
        for <joris.at.lebbeke@skynet.be>; Fri, 1 Oct 2004 16:16:15 +0200
        (envelope-from <tiff-bounces@remotesensing.org>)
Received: from adsl-065-083-169-202.sip.mco.bellsouth.net (localhost [127.0.0.1])
	by xserve.flids.com (Postfix) with ESMTP
	id 4584A343791; Fri,  1 Oct 2004 10:15:54 -0400 (EDT)
X-Original-To: tiff@remotesensing.org
Delivered-To: tiff@remotesensing.org
Received: from outmx006.isp.belgacom.be (outmx006.isp.belgacom.be
	[195.238.2.99])
	by xserve.flids.com (Postfix) with ESMTP id F3F3434376E
	for <tiff@remotesensing.org>; Fri,  1 Oct 2004 10:15:51 -0400 (EDT)
Received: from outmx006.isp.belgacom.be (localhost [127.0.0.1])
	by outmx006.isp.belgacom.be (8.12.11/8.12.11/Skynet-OUT-2.22) with
	ESMTP id i91EForl002389
	for <tiff@remotesensing.org>; Fri, 1 Oct 2004 16:15:50 +0200
	(envelope-from <joris.at.lebbeke@skynet.be>)
Received: from dfgrrxsknr4e (232.200-201-80.adsl.skynet.be [80.201.200.232])
	by outmx006.isp.belgacom.be (8.12.11/8.12.11/Skynet-OUT-2.22) with SMTP
	id i91EFhQh002338; Fri, 1 Oct 2004 16:15:43 +0200
	(envelope-from <joris.at.lebbeke@skynet.be>)
Message-ID: <001201c4a7c1$6e6165a0$e8c8c950@dfgrrxsknr4e>
From: "Joris" <joris.at.lebbeke@skynet.be>
To: "Frank Warmerdam" <warmerdam@pobox.com>
References: <000901c4a79d$5c0e6d90$51d0f151@dfgrrxsknr4e><415D5CFF.9010000@pobox.com><004801c4a7bd$79f56780$e8c8c950@dfgrrxsknr4e>
	<415D625F.5090107@pobox.com>
Subject: Re: [Tiff] quad-tile
Date: Fri, 1 Oct 2004 16:17:38 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Cc: Tiff mailing list <tiff@remotesensing.org>
X-BeenThere: tiff@remotesensing.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: TIFF and libtiff discussion  <tiff.remotesensing.org>
List-Unsubscribe: <http://xserve.flids.com/mailman/listinfo/tiff>,
	<mailto:tiff-request@remotesensing.org?subject=unsubscribe>
List-Archive: <http://xserve.flids.com/pipermail/tiff>
List-Post: <mailto:tiff@remotesensing.org>
List-Help: <mailto:tiff-request@remotesensing.org?subject=help>
List-Subscribe: <http://xserve.flids.com/mailman/listinfo/tiff>,
	<mailto:tiff-request@remotesensing.org?subject=subscribe>
Sender: tiff-bounces@remotesensing.org
Errors-To: tiff-bounces@remotesensing.org
X-UIDL: d00709339fec54718c1204b028530476

> The libtiffpic suite (thats where you got this, right?)

This particular file comes from a compressed file named 'pics-3.6.1.tar.gz',
that in turn comes from some LibTiff place (don't recall where exactly, but
somewhere on your pages for sure). I seem to remember the was a similar
testsuite in the 3.5.7 days, that also contained variants of this same image,
though I never bothered to look at the tagsets more closely at that time. So
probably its been around for quite a while. So if 'libtiffpic suite' is anything
new, than you're referring to a source I know nothing about and this image did
not come from.

> includes a variety of
> "problem" TIFF files that are non-standard as well as various standards
> compliant files.  While I don't recall all the history, I assume they exist
> so we have samples of the weird variants to help us maintain various hacks
> required to make them work.

I understand.

> So, I think the better solution might be to segregate our suite of test images
> into files considered to be standard and valid, and those that are invalid but
> that we want to work with anyways for purposes of interoperability.

Yes, absolutely defenetly.

> I have been leaving the sample image management up to Andrey though, so
> perhaps he will have further thoughts.  I do believe he is planning to augment
> the set of test images as he works on a libtiff test suite.

Ah, I was toying with the same idea. Seeing I can contribute so little C (let
alone makefiles ;-)), perhaps this way I can ease Andrey's workload? If not,
perhaps I can at least contribute a suggestion: a HTML index into the testimage,
explaining what is what, and what is valid, and including tag dumps (and maybe
even a reference thumbnail in a HTML-friendly and independent format like PNG)
could increase the usefullness of a testimage suite tremendously.



Joris Van Damme
info@awaresystems.be
http://www.awaresystems.be
Download your free TIFF tag viewer for windows here:
http://www.awaresystems.be/imaging/tiff/astifftagviewer.html

_______________________________________________
Tiff mailing list
Tiff@remotesensing.org
http://xserve.flids.com/mailman/listinfo/tiff
