[Gdal-dev] RE: Strange NoData value from a MrSID image (Peng Gao)

Michael P. Gerlek mpg at lizardtech.com
Fri Jun 24 14:42:58 EDT 2005

Frank, Peng:

In the MrSID SDK, we are not band-specific -- that is, a pixel is considered nodata iff all bands match the given values.


-----Original Message-----
From: Frank Warmerdam [mailto:fwarmerdam at gmail.com]
Sent: Friday, June 24, 2005 10:57 AM
To: Peng Gao
Cc: Michael P. Gerlek; gdal-dev at xserve.flids.com
Subject: Re: [Gdal-dev] RE: Strange NoData value from a MrSID image
(Peng Gao)

On 6/24/05, Peng Gao <pgao at esri.com> wrote:
> I have a question about the interpretation of MrSID NoData value. 
> Is a pixel considered NoData only if all three values match their 
> corresponding band NoData value, or Is a pixel considered NoData 
> if any band value matches band NoData value? For example, given 
> NoData values (0, 0, 0), Are only those pixels with value (0, 0, 0) 
> considered NoData, or (0, x, x), (0, 0, x), and etc considered 
> as NoData pixels as well? 


In the GDAL data model, nodata is band specific.  So if band one
has a nodata value of 0, then that band is considered to be nodata
if the pixel value is zero.  A pixel might well be no data in some bands,
and not in others ... at least in theory.

I'm not sure if this is the normal interpretation in MrSID though. 

Best regards, 
I set the clouds in motion - turn up   | Frank Warmerdam, warmerdam at pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush    | Geospatial Programmer for Rent

More information about the Gdal-dev mailing list