Oyvind,<br><br>GDAL handles nodata values band by band, whereas in MrSID all the bands of the particular pixel location must match the nodata values for that pixel to be considered nodata.<br>Currently nodata values are ignored in this driver. I don't know if anything is planned for future releases.<br>
<br><div class="gmail_quote">On Thu, Oct 28, 2010 at 4:21 PM, Oyvind Idland <span dir="ltr"><<a href="mailto:oyvind.idland@gmail.com">oyvind.idland@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hello,<br><br>stumbled across a problem when reading MrSid: <br><br>The MrSid dataset contains 3 bands, R/G/B. None of the 3 bands gives me a GetNoDataValue(),<br>however, the metadata contains IMAGE__NO_DATA_VALUE=255,255,255. <br>
<br>Does this mean, that I have to check for both cases ?<br><br>The version is GDAL 1.7.2.<br><br><br>Regards,<br><font color="#888888"><br><br>Oyvind Idland<br>
</font><br>_______________________________________________<br>
gdal-dev mailing list<br>
<a href="mailto:gdal-dev@lists.osgeo.org">gdal-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/gdal-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/gdal-dev</a><br></blockquote></div><br><br clear="all"><br>-- <br>Best regards,<br>Chaitanya kumar CH.<br>
/tʃaɪθənjə/ /kʊmɑr/ <br>+91-9494447584<br>17.2416N 80.1426E<br>