https://issues.qgis.org/https://issues.qgis.org/favicon.ico2012-10-11T06:46:49ZQGIS Issue TrackingQGIS Application - Bug report #6496: Wrong min/max values for rastershttps://issues.qgis.org/issues/6496?journal_id=364452012-10-11T06:46:49ZRadim Blazekradim.blazek@gmail.com
<ul></ul><p>It seems that GDALGetRasterStatistics() is giving cached estimated statistics if called with bApproxOK=false and bForce=false if exact statistics (from all raster pixels) are not available.</p>
<p>I have sent a question to GDAL list:<br /><a class="external" href="http://lists.osgeo.org/pipermail/gdal-dev/2012-October/034318.html">http://lists.osgeo.org/pipermail/gdal-dev/2012-October/034318.html</a></p> QGIS Application - Bug report #6496: Wrong min/max values for rastershttps://issues.qgis.org/issues/6496?journal_id=364492012-10-11T08:30:41ZRadim Blazekradim.blazek@gmail.com
<ul><li><strong>Resolution</strong> set to <i>fixed</i></li><li><strong>Status</strong> changed from <i>Open</i> to <i>Closed</i></li></ul><p>Fixed in <a class="changeset" href="https://issues.qgis.org/projects/qgis/repository/revisions/9ad9f8c08233e45b0c463eb0e246e065456167ca" title="fixed #6496 - wrong GDAL exact stats">9ad9f8c</a>.</p>
<p>Unfortunately GDAL does not seem to be able to recognize if its cached stats are estimated or exact, so we have to force recalculation if exact stats are requested in QGIS even if exact stats are cached by GDAL (we cannot be sure that are exact).</p>