<font face="courier new,monospace">Hello,<br>I have been working on ticket #3797. In the example given, gdalinfo is the calling the netcdf driver. I agree with Frank's opinion on this in ticket #1660:<br></font><br>
<blockquote style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;" class="gmail_quote">Note that GDALRasterBand has methods to get the offset and scale. The
normal GDAL practice would be to return them via those methods - not to
apply them on the fly. Then it is up to the caller to do so if they
wish.
<br></blockquote><br><font face="courier new,monospace">gdal shouldn't be in charge of scaling the data to what may be a different data type, or unpacking it. But in this case, gdalinfo is the caller. Should the functionality of the scaling be added to gdalinfo? Maybe optionally reporting the stats as scaled data? Any thoughts?<br clear="all">
</font><br># ============================<br>Kyle Shannon<br>Physical Science Technician<br>RMRS Fire Sciences Lab<br>Fire, Fuels & Smoke - RWU 4405<br>5775 Highway 10 W.<br>Missoula, MT 59808<br>(406)829-6954<br><a href="mailto:kshannon@fs.fed.us">kshannon@fs.fed.us</a><br>
# ============================<br>