Status: Read
Received: from [207.176.88.85] by phillip.cerious.com (NTMail 3.03.0017/7.aaxh) with ESMTP id pcrews for <pcrews@cerious.com>; Sat, 10 Jun 2000 10:41:28 -0400
Received: from localhost (daemon@localhost)
	by gate7.olympiakos.com (8.9.3/8.9.3) with SMTP id KAA03234;
	Sat, 10 Jun 2000 10:12:59 -0400
Received: by gate7.olympiakos.com (bulk_mailer v1.9); Sat, 10 Jun 2000 10:11:05 -0400
Received: (from majordom@localhost)
	by gate7.olympiakos.com (8.9.3/8.9.3) id KAA03156
	for tiff-outgoing; Sat, 10 Jun 2000 10:11:04 -0400
X-Authentication-Warning: gate7.olympiakos.com: majordom set sender to owner-tiff@olympiakos.com using -f
Received: from mail1.rdc2.on.home.com (mail1.rdc2.on.home.com [24.9.0.40])
	by gate7.olympiakos.com (8.9.3/8.9.3) with ESMTP id KAA03153
	for <tiff@olympiakos.com>; Sat, 10 Jun 2000 10:11:02 -0400
Received: from home.com ([24.68.88.161]) by mail1.rdc2.on.home.com
          (InterMail vM.4.01.03.00 201-229-121) with ESMTP
          id <20000610141051.JUSN26568.mail1.rdc2.on.home.com@home.com>;
          Sat, 10 Jun 2000 07:10:51 -0700
Message-ID: <39425A9C.A27A14B4@home.com>
Date: Sat, 10 Jun 2000 10:11:24 -0500
From: Frank Warmerdam <warmerda@home.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: Ivo_1 <ivo.penzar@infolink-software.com>
CC: TIFF Mailing List <tiff@olympiakos.com>
Subject: Re: Add: Resized version
References: <394225EC.C17B933C@infolink-software.com> <39423F5C.BE392BBA@infolink-software.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-tiff@olympiakos.com

Ivo_1 wrote:
> In fact, Compression tag is also missing for IFDs 1 to 5. libtiff concluded
> uncompressed data (default), but "optirastoras" meant Fax4 - as specified
> for the full size bitmap stored in IFD 0. That was actually the cause for
> TIFFReadTile() to fail with IFD 5 (should have debugged it).
> 
> Anyway, I am still asking for your opinions about "industry standard" usage
> and support for multiresolution TIFF images. E.g., which standard apps would
> create them, do they allow for user to specify what resized bitmaps to
> create, of which photometric type, etc. Also, do you know of multiple page
> TIFF files containing resized versions for some/all of its pages. I.e., some
> IFD tags would have bit 0 raised up, some bit 1 raised up, and some both
> (?!) - not to mention their possible masks: NewSubfileType bit 2 raised up.
> I am still not sure would that be compliant with TIFF rev. 5 (6), not to
> mention which standard apps would support them. Specially I am not quite
> sure which standard TIFF readers actually use those resize bitmaps to speed
> up stretching and so. And for TIFF editors: would they then really update
> both the original image and its resized version(s)?!

Ivo,

I would agree with your assessment that the optiras images are broken.  To 
my understanding the reduced resolution images are required to be fully 
formed images on their own, with their IFD fulfilling all the normal
TIFF requirements. 

I don't know much about the document imaging area or some other TIFF 
applications, but there is some use of multi-resolution TIFF files in the
satellite imaging area.  For instance the PCI, Intergraph and Global Geomatics
GeoTIFF readers all support reduced resolution images for accelerated 
display.  

I have written a small application called ``tiffaddo'', found in the 
libtiff/contrib directory for building reduced resolution images; however,
it only works for images with eight or more bits per pixel. 

It is my hope that satellite (and airphoto) data providers who ship GeoTIFF
files now can be persuaded in time to ship images with reduced resolution
overviews.

Best regards,

---------------------------------------+--------------------------------------
I set the clouds in motion - turn up   | Frank Warmerdam, warmerda@home.com
light and sound - activate the windows | http://members.home.com/warmerda
and watch the world go round - Rush    | Geospatial Programmer for Rent
