Received: from inav036.isp.belgacom.be (localhost.localdomain [127.0.0.1])
	by inav036.isp.belgacom.be (Postfix) with ESMTP id 17E54B2FAE
	for <joris.at.lebbeke@skynet.be>; Fri, 22 Dec 2006 18:58:32 +0100 (CET)
Received: from inas017.isp.belgacom.be (inas017.isp.belgacom.be [195.238.4.130])
	by inav036.isp.belgacom.be (Postfix) with ESMTP id 0B9BBB2F96
	for <joris.at.lebbeke@skynet.be>; Fri, 22 Dec 2006 18:58:32 +0100 (CET)
Received: from inmx003.isp.belgacom.be (inmx003.isp.belgacom.be [195.238.5.11])
        by inas017.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-IN-AS-2.03) with ESMTP id kBMHwLAD027054
        for <joris.at.lebbeke@skynet.be>; Fri, 22 Dec 2006 18:58:25 +0100
        (envelope-from <tiff-bounces@lists.maptools.org>)
Received: from duke.maptools.org (r153.dmsolutions.ca [209.217.116.153] (may be forged))
        by inmx003.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-IN-2.32) with ESMTP id kBMHwGHn027842
        for <joris.at.lebbeke@skynet.be>; Fri, 22 Dec 2006 18:58:16 +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 kBMHotwb012691;
	Fri, 22 Dec 2006 12:51:32 -0500
Received: from outmx007.isp.belgacom.be (outmx007.isp.belgacom.be
	[195.238.5.234])
	by duke.maptools.org (8.12.11/8.12.10) with ESMTP id kBMHorTT012688
	for <tiff@lists.maptools.org>; Fri, 22 Dec 2006 12:50:53 -0500
Received: from outmx007.isp.belgacom.be (localhost [127.0.0.1])
	by outmx007.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-OUT-2.22)
	with ESMTP id kBMHogKH029913
	for <tiff@lists.maptools.org>; Fri, 22 Dec 2006 18:50:42 +0100
	(envelope-from <joris.at.lebbeke@skynet.be>)
Received: from dfgrrxsknr4e (178.161-246-81.adsl-dyn.isp.belgacom.be
	[81.246.161.178])
	by outmx007.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-OUT-2.22)
	with SMTP id kBMHoXsR029836
	for <tiff@lists.maptools.org>; Fri, 22 Dec 2006 18:50:33 +0100
	(envelope-from <joris.at.lebbeke@skynet.be>)
Message-ID: <002901c725f1$c2c365c0$b2a1f651@dfgrrxsknr4e>
From: "Joris" <joris.at.lebbeke@skynet.be>
To: "TIFF mailing list" <tiff@lists.maptools.org>
Date: Fri, 22 Dec 2006 18:50:00 +0100
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.1807
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1896
Subject: [Tiff] BigTIFF implementation project - seeking one additional
	sponsor
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.00001e9e
X-MSP-STORE: Fri, 22 Dec 2006 18:58:32 +0100
Status:   

Folks,


Most of you probably remember the BigTIFF discussions... Not too long
ago, this community developed a specification for an extension to TIFF
to use 64bit offsets within a new variation of the format now referred
to as BigTIFF.  This allows file sizes up to 18000 petabytes,
effectively infinite.  This specification was developed with input from
a variety of sources, including users of the libtiff library,
representatives of Adobe (the owner of the TIFF specification) and
developers of other TIFF codecs.

The BigTIFF specification has been successfully implemented my own
proprietary AWare Systems TIFF codec.  However, the LibTiff development
team, myself included, has not been able to find the several months of
development time required to implement support for BigTIFF in the
LibTiff library.

I have agreed to implement a BigTIFF upgrade for LibTiff if reasonable
financial support can be found for the project.  To that end the
"BigTIFF Sponsorship" effort was launched.  It is described at:

   http://www.remotesensing.org/libtiff/BigTIFFProposal.html

So far we have been quite successful and have secured commitments from
three of four needed sponsors, each for an amount of $6000 USD towards
the project. This email is a solicitation for one final sponsor for the
same amount so that we can launch the development project in February.

The proposal page above covers the details, but the gist is that the
project will result in a LibTiff 4.0 circa July 2007 that will support
reading traditional TIFF files, as well as BigTIFF files, and will
support writing either variant.

This is an appeal from me then for one additional organization in our
industry to step forward to support this important infrastructural
project.

In addition to the technical benefits this project will bring, I believe
the project press release will also bring a reputational benefit to all
the sponsors. Additionally, I have agreed to throw in up to 20 hours of
consulting and support, per sponsor, on any BigTIFF migration issues
that a sponsor may be facing, and/or any additional related requests
they may have.

Please contact myself or Frank Warmerdam if you are interested in taking
the last sponsorship position so that we can launch the project on time.


Best regards,

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@lists.maptools.org
http://lists.maptools.org/mailman/listinfo/tiff
http://www.remotesensing.org/libtiff/
