AWARE [SYSTEMS] Imaging expertise for the Delphi developer
AWare Systems, Imaging expertise for the Delphi developer, Home TIFF and LibTiff Mailing List Archive

LibTiff Mailing List

TIFF and LibTiff Mailing List Archive
January 2007

Previous Thread
Next Thread

Previous by Thread
Next by Thread

Previous by Date
Next by Date

Contact

The TIFF Mailing List Homepage
This list is run by Frank Warmerdam
Archive maintained by AWare Systems



Valid HTML 4.01!



Thread

2007.01.17 02:25 "Elevation Data", by Craig Bruce
2007.01.17 02:57 "Re: Elevation Data", by Bob Friesenhahn
2007.01.17 08:07 "Re: Elevation Data", by Joris Van Damme
2007.01.17 15:24 "Re: Elevation Data", by Ed Grissom
2007.01.17 15:55 "Re: Elevation Data", by Joris Van Damme
2007.01.17 16:03 "Re: Elevation Data", by Ed Grissom
2007.01.17 16:20 "Re: Elevation Data", by Joris Van Damme
2007.01.17 16:52 "Re: Elevation Data", by Ed Grissom
2007.01.17 17:20 "Re: Elevation Data", by Joris Van Damme
2007.01.17 19:26 "Re: Elevation Data", by Ed Grissom
2007.01.17 20:22 "Re: Elevation Data", by Joris Van Damme
2007.01.17 20:52 "Re: Elevation Data", by Joris Van Damme
2007.01.17 21:00 "Re: Elevation Data", by Bob Friesenhahn
2007.01.17 21:58 "Re: Elevation Data", by Joris Van Damme
2007.01.17 22:18 "Re: Elevation Data", by Bob Friesenhahn
2007.01.18 11:09 "Re: Elevation Data", by Andrey Kiselev
2007.01.17 20:00 "Re: Elevation Data", by Craig Bruce
2007.01.17 17:01 "Re: Elevation Data", by Bob Friesenhahn
2007.01.17 18:35 "Re: Elevation Data", by Joris Van Damme
2007.01.17 21:08 "Re: Elevation Data", by Frank Warmerdam
2007.01.17 19:27 "Re: Elevation Data", by Frank Warmerdam
2007.01.17 16:08 "Re: Elevation Data", by Bob Friesenhahn
2007.01.17 16:30 "Re: Elevation Data", by Joris Van Damme
2007.01.17 19:03 "Re: Elevation Data", by Frank Warmerdam
2007.01.17 17:28 "Re: Elevation Data", by Joris Van Damme
2007.01.17 21:18 "Re: Elevation Data", by Frank Warmerdam
2007.01.17 16:51 "Re: Elevation Data", by Gerben Vos
2007.01.17 18:03 "Re: Elevation Data", by Joris Van Damme
2007.01.17 16:27 "Re: Elevation Data", by Frank Warmerdam
2007.01.17 19:00 "Re: Elevation Data", by Joris Van Damme
2007.01.17 21:51 "Re: Elevation Data", by Frank Warmerdam
2007.01.17 03:35 "Re: Elevation Data", by Frank Warmerdam
2007.01.17 08:00 "Re: Elevation Data", by Joris Van Damme
2007.01.17 20:07 "Re: Elevation Data", by Joris Van Damme

2007.01.17 20:07 "Re: Elevation Data", by Joris Van Damme

Frank,

Thanks for commenting on the proposed recommendation.

Unfortunately, I can't agree with anything but the very last part.

> My concern is with this statement:
>
> """
> It is also valid, and recommended as a second best choice, to use any
> other range. In this case, writing out the SMin/SMax tag is
> obligatory.
> """
>
> My concern is that it conflicts with widespread existing usage which
> is to write out data such as elevation with a photometric
> interpretation of MINISBLACK and no SMin/SMax values.
>
> I would prefer the statement to read as:
>
> """
> It is also valid, and recommended as a second best choice, to use any
> other range. In this case, writing out the SMin/SMax tag is
> encouraged.
> """

Yeah, but, this is a writer recommendation. Writers make mistakes all
the time. The thing is, the recommendation reflects the fact that
readers aren't logically able to resolve the situation if they don't
known the writers range intention first hand.

> I also have no intention of following the following reader advice:
>
> """
> If the SMin/SMax tags aren't present, readers are recommended to take
> that as a firm indication the standard 'intrinsic' range is use.
> """

That may be perfectly fine in your realm of application, but it
conflicts with interchange of image data... I think. Writers may write
high-range data or partial-gamut-using data in the 'intrinsic' range,
and not specify SMin/SMax tag, and unless you take the absence of those
tags to mean that the instinsic range is used, you don't get their
range intention but their actual encoded range instead. This is the case
for the biggest part of the few files in my test file library.

> So, all things considered I'm inclined to leave things in the current
> ill defined state which is working fine for me rather than commit to
> your language.

Well, I've no personal gain here and I've spend too much time already in
my quixotic concerns for open formats and interchange. Ill defined state
it is.


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