<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'>Jukka/Even,<br><br>Yes, you guy are right. The "-a_nodata none" will help but I still need to implement a value range check on my CreateCopy anyway. So users don't need to run gdal_translate again after they find the problem or use "-a_nodata none" all the time (in a script for example) and miss the good ones.<br><br>Thanks.<br><br><div>> To: gdal-dev@lists.osgeo.org<br>> From: jukka.rahkonen@maanmittauslaitos.fi<br>> Date: Tue, 19 May 2015 13:43:38 +0000<br>> Subject: Re: [gdal-dev] RFC 58: Removing Dataset Nodata Value<br>> <br>> Ivan Lucena <lucena_ivan <at> hotmail.com> writes:<br>> <br>> > Would that be feasible to accept the option "-a_nodata NO" on GDAL command<br>> lines, to indicate that NoData should not pass from the input to the output<br>> dataset?<br>> <br>> Would it be something different than "-a_nodata none"?<br>> <br>> -a_nodata value:<br>> Assign a specified nodata value to output bands. Starting with GDAL<br>> 1.8.0, can be set to none to avoid setting a nodata value to the output file<br>> if one exists for the source file. Note that, if the input dataset has a<br>> nodata value, this does not cause pixel values that are equal to that nodata<br>> value to be changed to the value specified with this option. <br>> <br>> -Jukka Rahkonen-<br>> <br>> _______________________________________________<br>> gdal-dev mailing list<br>> gdal-dev@lists.osgeo.org<br>> http://lists.osgeo.org/mailman/listinfo/gdal-dev<br></div> </div></body>
</html>