<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Hi Vicent,<br><br>Since the SetNoDataValue and GetNodataValue is based on the limitation of GeoTiff I would not expect DeleteNoDataValue to be any different. For example, there is no way to set/get NoData for individuals bands, there is no way to set/get an array of NoData values or NoData value ranges. For drivers that support such thinks, the DeleteNoDataValue will probably delete all NoData values from the dataset.<br><br>But that is something that can't be resolved by the RFC 58. I think.<br><br>Very often, I find unsigned 8 bit images with absurd NoData value, like -9999. That is probably a software specific flag value. The problem is that in gdal_translate there is no option to prevent that NoData to be passed from one format to another. So I am about to implement a value range check on the CreateCopy to avoid that.<br><br>Would that be feasible to accept the option "-a_nodata NO" on GDAL command lines, to indicate that NoData should not pass from the input to the output dataset?<br><br>Best regards,<br><br>Ivan<br><br><br><div><hr id="stopSpelling">Date: Tue, 19 May 2015 08:50:50 +0200<br>From: schut@sarvision.nl<br>To: gdal-dev@lists.osgeo.org<br>Subject: Re: [gdal-dev] RFC 58: Removing Dataset Nodata Value<br><br>
On 05/18/2015 08:37 PM, Sean Gillies wrote:<br>
<blockquote cite="mid:CADPhZXy54dxXZ61gJeszo-aw722B4Ogb0VBV_zwJQg9SrS4bEQ@mail.gmail.com">
<div dir="ltr">Hi all,
<div><br>
</div>
<div>In consultation with Even Rouault, I've written up RFC 58. </div>
<div><br>
</div>
<div> <a href="https://trac.osgeo.org/gdal/wiki/rfc58_removing_dataset_nodata_value" target="_blank">https://trac.osgeo.org/gdal/wiki/rfc58_removing_dataset_nodata_value</a></div>
<div><br>
</div>
<div>The gist of it: allowing deletion of a nodata value defined
for a dataset, thereby rendering all pixels valid without
copying data to a new file.</div>
<div><br>
</div>
<div>I'd love your feedback and thumbs up or thumbs down on this
RFC. Thanks,</div>
</div>
</blockquote>
As daily users of gdal me and my collegues would like to give this a
very big thumbs up. We've really been missing this. Thanks a lot for
starting this RFC.<br>
<br>
Vincent.<br>
<br>
<blockquote cite="mid:CADPhZXy54dxXZ61gJeszo-aw722B4Ogb0VBV_zwJQg9SrS4bEQ@mail.gmail.com">
<div dir="ltr">
<div><br>
</div>
<div>--</div>
<div>Sean Gillies</div>
<div><br>
</div>
<div><br>
</div>
</div>
<br>
<fieldset class="ecxmimeAttachmentHeader"></fieldset>
<br>
<pre>_______________________________________________
gdal-dev mailing list
<a class="ecxmoz-txt-link-abbreviated" href="mailto:gdal-dev@lists.osgeo.org">gdal-dev@lists.osgeo.org</a>
<a class="ecxmoz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/gdal-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/gdal-dev</a></pre>
</blockquote>
<br>
<br>_______________________________________________
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev</div> </div></body>
</html>