Return-Path: <tiff-bounces@lists.maptools.org>
Received: from inas026.isp.belgacom.be (localhost [127.0.0.1])
        by inav017.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-AV-3.00) with ESMTP id j8G4LwCi024367
        for <joris.at.lebbeke@skynet.be>; Fri, 16 Sep 2005 06:21:58 +0200
        (envelope-from <tiff-bounces@lists.maptools.org>)
Received: from inmx020.isp.belgacom.be (inmx020.isp.belgacom.be [195.238.3.139])
        by inas026.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-AS-2.03) with ESMTP id j8G4Lsxp017104
        for <joris.at.lebbeke@skynet.be>; Fri, 16 Sep 2005 06:21:55 +0200
        (envelope-from <tiff-bounces@lists.maptools.org>)
Received: from duke.maptools.org (r153.dmsolutions.ca [209.217.116.153] (may be forged))
        by inmx020.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-2.32) with ESMTP id j8G4Ln69022309
        for <joris.at.lebbeke@skynet.be>; Fri, 16 Sep 2005 06:21:49 +0200
        (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 j8G4CwiH003823;
	Fri, 16 Sep 2005 00:13:09 -0400
Received: from outmx020.isp.belgacom.be (outmx020.isp.belgacom.be
	[195.238.2.201])
	by duke.maptools.org (8.12.11/8.12.10) with ESMTP id j8G4CtQd003820
	for <tiff@lists.maptools.org>; Fri, 16 Sep 2005 00:12:56 -0400
Received: from outmx020.isp.belgacom.be (localhost [127.0.0.1])
	by outmx020.isp.belgacom.be (8.12.11/8.12.11/Skynet-OUT-2.22) with
	ESMTP id j8G4Cqjk032418
	for <tiff@lists.maptools.org>; Fri, 16 Sep 2005 06:12:52 +0200
	(envelope-from <joris.at.lebbeke@skynet.be>)
Received: from dfgrrxsknr4e (24-129.246.81.adsl.skynet.be [81.246.129.24])
	by outmx020.isp.belgacom.be (8.12.11/8.12.11/Skynet-OUT-2.22) with SMTP
	id j8G4Ckv1032379; Fri, 16 Sep 2005 06:12:47 +0200
	(envelope-from <joris.at.lebbeke@skynet.be>)
Message-ID: <000801c5ba74$f87ecf40$1881f651@dfgrrxsknr4e>
From: "Joris" <joris.at.lebbeke@skynet.be>
To: "katrina maramba" <ka3na_423@yahoo.com>, <tiff@lists.maptools.org>
References: <20050916032536.19460.qmail@web60221.mail.yahoo.com>
Subject: Re: [Tiff] What do you call...
Date: Fri, 16 Sep 2005 06:13:16 +0200
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.00000c23
X-MSP-STORE: Fri, 16 Sep 2005 06:22:00 +0200
Status:   

katrina maramba wrote:
> I know this isn't Baseline Tiff since Baseline Tiff
> doesn't care where the location of the directory is.
> Is there another term that would describe this
> functionality?  Or would "only images generated from
> the camera is supported" enough and can be understood
> by everyone?

No. Digital camera software that generates TIFFs, too, can put the first
IFD any place they like. Possibly, the camera software/driver/whatever
that you have tested puts it at a specific location. Other camera's or
even other software/driver/whatever for the same may behave differently.
Even the camera's you've tested may behave differently in some specific
situation, there's no way to know for sure other then reverse
engineering them. And also, possibly 'those that were manipulated in the
PC or any software', that you've tested, put the first IFD at a location
other then offset 8, but other PC software may behave differently and
put it at offset 8.

If you impose this kind of limitation, it is likely you haven't thought
of ColorMap data, for instance, or any other situation that makes
crucial data larger then 4 bytes, like having multiple strips or tiles,
because all those data blocks too, can be located just anywhere and
you're obviously depending on fixed order and position. In short, you're
likely supporting a few odd files from a single source only. There's no
term for that. You would best describe it as 'seems to support output
from this or that particular version of this or that particular camera,
as far as tested'.

Sorry, but that's just what you get if you ignore the spec on an
extremely basic pillar property of the file format you wish to support.


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/
