[mapserver-users] ArcInfo TIFF byte order

[Antti.Roppola at brs.gov.au]

Interesting...

I have noticed that TIFFs I create using ArcInfo on
Solaris will not work on my x86 Linux box unless I flip
the byte order from big-endian to little-endian. This
behaviour wasn't noticed in Mapserver 3.3, which didn't
seem to care (I just check and I have a mix of both types
depending on what app produced the TIFF)

I presume this is because I am using GDAL's TIFF support
rather than Mapserver's internal TIFF support, and GDAL
is picky about byte order.

Is this the case? Or is my loading of TIFFs into Gimp doing
something else besides swapping the byte-order? I suspect not
because I can't load big-endian TIFFs that work OK in v3.3.

Cheers,

Antti