Return-Path: <tiff-bounces@lists.maptools.org>
Received: from mailgate001.isp.belgacom.be (mailgate001.isp.belgacom.be [195.238.6.86])
        by maildelivery012.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-IN-2.32) with ESMTP id l63EaSiW009482
        for <joris.at.lebbeke@skynet.be>; Tue, 3 Jul 2007 16:36:28 +0200
        (envelope-from <tiff-bounces@lists.maptools.org>)
Received: from r153.dmsolutions.ca (HELO duke.maptools.org) ([209.217.116.153])
  by in.mx.skynet.be with ESMTP; 03 Jul 2007 16:36:27 +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 l63EO3xf023563;
	Tue, 3 Jul 2007 10:24:15 -0400
Received: from dns2.namehog.net (dns2.namehog.net [213.52.234.203])
	by duke.maptools.org (8.12.11/8.12.10) with ESMTP id l63ENvKx023560
	for <tiff@lists.maptools.org>; Tue, 3 Jul 2007 10:23:58 -0400
Received: from 81-86-57-99.dsl.pipex.com ([81.86.57.99] helo=EKAT)
	by dns2.namehog.net with esmtpa (Exim 4.66)
	(envelope-from <andy.cave@hamillroad.com>)
	id 1I5jIV-0008Qo-Tm; Tue, 03 Jul 2007 15:24:08 +0100
Message-ID: <021b01c7bd7d$c6dcf6c0$da60fea9@EKAT>
From: "Andy Cave" <andy.cave@hamillroad.com>
To: "Frank Warmerdam" <warmerdam@pobox.com>
References: <AD092979-0113-1000-9184-11F5B78AE269-Webmail-10016@mac.com><001701c7bd5f$33b87d60$0201a8c0@AWareCore2Duo>
	<000901c7bd6b$e3d90730$0201a8c0@AWareCore2Duo>
	<014901c7bd6d$526a94b0$da60fea9@EKAT>
	<001201c7bd6f$55f0c350$0201a8c0@AWareCore2Duo>
	<01b501c7bd72$655773e0$da60fea9@EKAT> <468A5546.5000106@pobox.com>
Subject: Re: [Tiff] Re: Big TIFF Compression
Date: Tue, 3 Jul 2007 15:23:48 +0100
Organization: Hamillroad Software
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-PopBeforeSMTPSenders: acave@hamillroad.com, news@hamillroad.com,
	sales@hamillroad.com, support@hamillroad.com
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - dns2.namehog.net
X-AntiAbuse: Original Domain - lists.maptools.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - hamillroad.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: tiff@lists.maptools.org
X-BeenThere: tiff@lists.maptools.org
X-Mailman-Version: 2.1.4
Precedence: list
Reply-To: Andy Cave <andy.cave@hamillroad.com>
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.000024ff
X-MSP-STORE: Tue, 03 Jul 2007 16:36:33 +0200
Status:   

Hi Frank,

Thanks. That's interesting info.

>From what you say, with the 16 bpp or float data types, I presume either LZW 
or Flate is used (if any).

It sounds like people currently don't write 1m x 1m pixels (and clearly 
probably don't since they'd exceed classic TIFFs file size), but might start 
trying to once BigTIFF is out. In comparison, pre-press separations at their 
largest are typically 100K - 150K (on each side) or thereabouts. Security 
printing does go up to 10,000 dpi, but then the page sizes are smaller, so 
overall dimensions not much different. This is unlikely to change (no real 
need for higher resolution - and even if you do, the halftone dots get 
bigger, so compressed data size is not that much different).

It will be interesting to track peoples experience as they do so, as I think 
a whole bunch of new issues will turn up (performance of reading/writing 
large files, OS limitations, corruption, copying these files around(!), 
ftp'ing them, etc...).

Regards,

Andy.

----- Original Message ----- 
From: "Frank Warmerdam" <warmerdam@pobox.com>
To: "Andy Cave" <andy.cave@hamillroad.com>
Cc: <tiff@lists.maptools.org>
Sent: Tuesday, July 03, 2007 2:55 PM
Subject: Re: [Tiff] Re: Big TIFF Compression


> Andy Cave wrote:
>> I presume that georeferencing and medical imaging are all 8 bits per 
>> pixel, multi-channel for the former (and possibly latter).
>
> Andy,
>
> Speaking for geospatial images, they are not all 8bit per pixel.  Many
> are 16bits per pixel (the IKONOS sensor for instance), and scientific
> data sometimes uses other data types (floating point for instance).
>
> Multi-channel (ie. multi-sample) is common but there are also a lot
> greyscale datasets (one sample per pixel).
>
>> I'm interested in hearing real examples as to why BigTIFF is useful for 
>> georeferencing and medical imaging. Are the images really that big? After 
>> compression or only without? Are they big 'cause they are multi-channel, 
>> or multi-page, or uncompressed, or, ...?
>
> Geospatial images are often mosaiced into seamless images for large
> regions.  As you can imagine an image with 1m x 1m pixels for the
> entire united states gets very large.  Previously other formats were
> used for this, or supertiling of many medium sized TIFF files.
>
> Best regards,
> -- 
> ---------------------------------------+--------------------------------------
> I set the clouds in motion - turn up   | Frank Warmerdam, 
> warmerdam@pobox.com
> light and sound - activate the windows | http://pobox.com/~warmerdam
> and watch the world go round - Rush    | President OSGeo, http://osgeo.org
> 


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