<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'><br><br><div>> From: even.rouault@spatialys.com<br>> To: gdal-dev@lists.osgeo.org<br>> Subject: Re: [gdal-dev] RFC 58: Removing Dataset Nodata Value<br>> Date: Tue, 19 May 2015 16:10:38 +0200<br>> CC: lucena_ivan@hotmail.com; jukka.rahkonen@maanmittauslaitos.fi<br>> <br>> Le mardi 19 mai 2015 16:06:59, Ivan Lucena a écrit :<br>> > Jukka/Even,<br>> > <br>> > Yes, you guy are right. The "-a_nodata none" will help but I still need to<br>> > implement a value range check on my CreateCopy anyway. So users don't need<br>> > to run gdal_translate again after they find the problem or use "-a_nodata<br>> > none" all the time (in a script for example) and miss the good ones.<br>> <br>> I'm wondering if it might not make more sense to modify the input driver(s) to <br>> not report out-of-range nodata values ? I fail to see a reason to report an <br>> out-of-range nodata value.<br>> <br><br>That makes sense but we would need to go though all drivers and copy&paste the value range check code to avoid reporting wrong values. Could the core GetNoDataValue do that instead?<br><br>> > <br>> > Thanks.<br>> > <br>> > > 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>> > > > Would that be feasible to accept the option "-a_nodata NO" on GDAL<br>> > > > command<br>> > > <br>> > > lines, to indicate that NoData should not pass from the input to the<br>> > > output 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>> > > <br>> > > 1.8.0, can be set to none to avoid setting a nodata value to the output<br>> > > file if one exists for the source file. Note that, if the input dataset<br>> > > has a nodata value, this does not cause pixel values that are equal to<br>> > > that nodata 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>> <br>> -- <br>> Spatialys - Geospatial professional services<br>> http://www.spatialys.com<br></div> </div></body>
</html>