AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2004.01.14 12:01 "[Tiff] COLORMAP and byte padding", by Stephan Assmus
2004.01.14 15:07 "Re: [Tiff] COLORMAP and byte padding", by Frank Warmerdam
2004.01.14 16:18 "Re: [Tiff] COLORMAP and byte padding", by Gerben Vos
2004.01.14 16:43 "Re: [Tiff] COLORMAP and byte padding", by Joris Van Damme
2004.01.14 17:13 "Re: [Tiff] COLORMAP and byte padding", by Gerben Vos
2004.01.14 17:17 "Re: [Tiff] COLORMAP and byte padding", by Joris Van Damme
2004.01.14 17:26 "Re: [Tiff] COLORMAP and byte padding", by Andy Cave
2004.01.14 17:36 "Re: [Tiff] COLORMAP and byte padding", by Joris Van Damme
2004.01.14 17:24 "Re: [Tiff] COLORMAP and byte padding", by Phillip Crews
2004.01.14 18:18 "Re: [Tiff] COLORMAP and byte padding", by Marti Maria
2004.01.14 19:02 "Re: [Tiff] COLORMAP and byte padding", by Andy Cave
2004.01.14 19:36 "Re: [Tiff] COLORMAP and byte padding", by Marti Maria
2004.01.14 19:48 "Re: [Tiff] COLORMAP and byte padding", by Andy Cave
2004.01.15 17:24 "Re: [Tiff] COLORMAP and byte padding", by Marti Maria
2004.01.15 17:37 "Re: [Tiff] COLORMAP and byte padding", by Andy Cave
2004.01.15 00:05 "Re: [Tiff] COLORMAP and byte padding", by Chris Cox

2004.01.14 17:26 "Re: [Tiff] COLORMAP and byte padding", by Andy Cave

I really wouldn't do that. The 'solution' of dividing by 256 is far more accurate.

With 256:

0 to 255 -> 0,
256 to 511 -> 1,
...
65280 to 65535 ->255.

This gives an even map of 256 values down to each resultant value.

With 257:

0 to 256 -> 0,
257 to 513 -> 2,
...
65278 to 65534 -> 254
65535 ->255.

NOT an even spread.

_andy.