Return-Path: <tiff-bounces@lists.maptools.org>
Received: from inas011.isp.belgacom.be (localhost [127.0.0.1])
        by inav006.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-AV-3.00) with ESMTP id jBDFUMTE031172
        for <joris.at.lebbeke@skynet.be>; Tue, 13 Dec 2005 16:30:22 +0100
        (envelope-from <tiff-bounces@lists.maptools.org>)
Received: from inmx019.isp.belgacom.be (inmx019.isp.belgacom.be [195.238.5.138])
        by inas011.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-AS-2.03) with ESMTP id jBDFUI3m008099
        for <joris.at.lebbeke@skynet.be>; Tue, 13 Dec 2005 16:30:19 +0100
        (envelope-from <tiff-bounces@lists.maptools.org>)
Received: from duke.maptools.org (r153.dmsolutions.ca [209.217.116.153] (may be forged))
        by inmx019.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-2.32) with ESMTP id jBDFU916023527
        for <joris.at.lebbeke@skynet.be>; Tue, 13 Dec 2005 16:30:09 +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 jBDF7sWk006961;
	Tue, 13 Dec 2005 10:09:22 -0500
Received: from outmx009.isp.belgacom.be (outmx009.isp.belgacom.be
	[195.238.5.4])
	by duke.maptools.org (8.12.11/8.12.10) with ESMTP id jBDF7pMn006958
	for <tiff@lists.maptools.org>; Tue, 13 Dec 2005 10:07:52 -0500
Received: from outmx009.isp.belgacom.be (localhost [127.0.0.1])
	by outmx009.isp.belgacom.be (8.12.11/8.12.11/Skynet-OUT-2.22) with
	ESMTP id jBDF7m7v009549
	for <tiff@lists.maptools.org>; Tue, 13 Dec 2005 16:07:48 +0100
	(envelope-from <joris.at.lebbeke@skynet.be>)
Received: from dfgrrxsknr4e (159-167.246.81.adsl.skynet.be [81.246.167.159])
	by outmx009.isp.belgacom.be (8.12.11/8.12.11/Skynet-OUT-2.22) with SMTP
	id jBDF7hV9009469; Tue, 13 Dec 2005 16:07:43 +0100
	(envelope-from <joris.at.lebbeke@skynet.be>)
Message-ID: <003301c5fff6$f7f7d860$9fa7f651@dfgrrxsknr4e>
From: "Joris" <joris.at.lebbeke@skynet.be>
To: "Paul J. Lucas" <pauljlucas@mac.com>, <tiff@lists.maptools.org>
References: <Pine.LNX.4.63.0512121417170.20603@vgfl.cnhywyhpnf.bet><Pine.SOC.4.60.0512121643050.4804@blade.simplesystems.org><Pine.LNX.4.63.0512121452030.20603@vgfl.cnhywyhpnf.bet><Pine.SOC.4.60.0512121747160.4804@blade.simplesystems.org><Pine.LNX.4.63.0512121813540.20603@vgfl.cnhywyhpnf.bet><001201c5ffa5$6db21040$e2abf551@dfgrrxsknr4e>
	<Pine.LNX.4.63.0512122344310.20603@vgfl.cnhywyhpnf.bet>
Subject: Re: [Tiff] Writing EXIF data?
Date: Tue, 13 Dec 2005 16:07:20 +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.1506
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
Cc: 
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.00000f62
X-MSP-STORE: Tue, 13 Dec 2005 16:30:28 +0100
Status:   

Paul,

Paul J. Lucas wrote:
> > I assume that is the reason why you feel the EXIF tag is
> > undocumented. It's documented allright
>
> It's in the header file, but not on the TIFFSetField manual
> page.  Hence, it's undocumented.

OK, then TIFFSetField on the EXIF tag is undocumented. I understood your
comment in another way. Mea culpa.

> > Not properly implementing tag namespaces, LibTiff has troubles with
> > this concept. How is it supposed to define GPSLatitudeRef, or, the
> > other way around, how is it supposed to make sense of tag ID code
> > 1, when it has
> > no clue 'bout namespaces?
>
> For EXIF at least, libtiff doesn't need to know anything about
> EXIF tags except the EXIF IFD pointer (which already has a
> #define for it in the header file).  I merely want to insert a
> blob of binary data into the TIFF file that's being created and
> have the EXIF IFD pointer point to it.  The libtiff library
> doesn't have to know or care about the contents of the blob.

You do realize the 'blob' is an IFD, as I tried to explain? Most people
want to use LibTiff to read and write the tags in that IFD, too. But if
you've done all that in another way, already, things may be easier, and
someone here may be able to point you in the right direction if a right
direction exists.

May I ask how you wrote that IFD that you refer to as 'blob'?

Sorry I can't be more helpful. My departement is mainly the file format,
not the library. I sense a little aggrevation, and I can understand
that, but apart from understanding there's little I can do. I recommend
you explain how you wrote the 'blob' and convince the right persons that
all you want is to set the EXIF tag value to a particular known offset.
If you've any funds for solving any problems that you may experience, I
recommend mentioning that too.


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/
