Return-Path: <tiff-bounces@lists.maptools.org>
X-Original-To: info@awaresystems.be
Delivered-To: info@awaresystems.be
Received: from mx-k.b-one.net (mx-k.one.com [91.198.169.58])
	by mail9.b-one.net (Postfix) with ESMTP id 3E42C40013D
	for <info@awaresystems.be>; Tue, 30 Jun 2009 15:35:36 +0200 (CEST)
X-Virus-Scanned: by one.com
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 tagged_above=0 required=6 tests=[none]
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4
Received: from lists.maptools.org (lists.maptools.org [65.39.174.144])
	by mx-k.b-one.net (Postfix) with ESMTP id B0D2FC2466F
	for <info@awaresystems.be>; Tue, 30 Jun 2009 15:35:35 +0200 (CEST)
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
	by lists.maptools.org (Postfix) with ESMTP id 0F3591D2C320C;
	Tue, 30 Jun 2009 08:35:04 -0500 (EST)
Received: from mailgw2a.lmco.com (mailgw2a.lmco.com [192.91.147.7])
	by lists.maptools.org (Postfix) with ESMTP id C74581D2C31F0
	for <tiff@lists.maptools.org>; Tue, 30 Jun 2009 08:34:32 -0500 (EST)
Received: from emss03g01.ems.lmco.com (relay3.ems.lmco.com [141.240.4.144])by
	mailgw2a.lmco.com (LM-6) with ESMTP id n5UDYTFr008362;
	Tue, 30 Jun 2009 09:34:30 -0400 (EDT)
Received: from CONVERSION2-DAEMON.lmco.com by lmco.com (PMDF V6.3-x14 #31428)
	id <0KM2002010D91O@lmco.com>; Tue, 30 Jun 2009 09:34:21 -0400 (EDT)
Received: from EMSS04I00.us.lmco.com ([166.17.13.135]) by lmco.com (PMDF
	V6.3-x14 #31428) with ESMTP id <0KM200EIX0CXO1@lmco.com>;
	Tue, 30 Jun 2009 09:34:16 -0400 (EDT)
Received: from emss04m23.us.lmco.com ([166.17.13.76]) by EMSS04I00.us.lmco.com
	with Microsoft SMTPSVC(5.0.2195.6713); Tue,
	30 Jun 2009 09:34:14 -0400
Date: Tue, 30 Jun 2009 09:34:14 -0400
From: "Richmond, Jim" <jim.richmond@lmco.com>
In-reply-to: <4A4A1312.4000605@pobox.com>
To: Frank Warmerdam <warmerdam@pobox.com>
Message-id: <0D237077B37CD943A64396032B65692710C34843@EMSS04M23.us.lmco.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Thread-Topic: [Tiff] Errors parsing TIFF/GeoTIFF files greater than 2GB
Thread-Index: Acn5hsD6BRX3LVAoRFKmR992B29R9AAAJ9yA
Content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <0D237077B37CD943A64396032B65692710C34796@EMSS04M23.us.lmco.com>
	<4A4A1312.4000605@pobox.com>
X-OriginalArrivalTime: 30 Jun 2009 13:34:14.0975 (UTC)
	FILETIME=[75D7D4F0:01C9F987]
Cc: tiff@lists.maptools.org
Subject: Re: [Tiff] Errors parsing TIFF/GeoTIFF files greater than 2GB
X-BeenThere: tiff@lists.maptools.org
X-Mailman-Version: 2.1.9
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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tiff-bounces@lists.maptools.org
Errors-To: tiff-bounces@lists.maptools.org

We're running with Solaris 10. 


-----Original Message-----
From: Frank Warmerdam [mailto:warmerdam@pobox.com] 
Sent: Tuesday, June 30, 2009 9:29 AM
To: Richmond, Jim
Cc: tiff@lists.maptools.org
Subject: Re: [Tiff] Errors parsing TIFF/GeoTIFF files greater than 2GB

Richmond, Jim wrote:
> Hi, we're using version 3.8.2 of the TIFF library (I think we'd 
> downloaded it from remotesensing.org) and are running into
> 
> problems parsing files greater than 2GB.  This is the first time that 
> we've ever dealt with files greater than this size.  Here's
> 
> the portion of our C++ code (it's been untouched for many years).
> 
> TIFF  *TIFFPtr = (TIFF *)0;
> 
> TIFFPtr = XTIFFOpen (imageFilename, "r");
> 
> retCode = TIFFGetField(TIFFPtr,  TIFFTAG_IMAGEWIDTH,  &myImageWidth);
> 
> It looks like either the call to XTIFFOpen is returning a null pointer

> or the call to TIFFGetField is returning a value of FALSE.  I've seen
> 
> references in the archives to other people with similar issues, but
was 
> wondering if there is some type of configuration value
> 
> that I can change in version 3.8.2 to get this to work. Thanks!

Jim,

What are you using for low level IO?  Is this using tif_win32.c on
windows?
tif_unix.c on linux? Solaris?   One issues at the 2GB barrier is
ensuring
that you are using a large file enabled file io implementation.  On
win32
the tif_unix implementation is 32bit and only up to 2GB.  On linux it
should
normally be 64bit.  On other unix platforms it may or may not support
large
files.  If you have implemented your own low level file IO layer for
some
reason, then that can also be an issue.

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    | Geospatial Programmer for Rent

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