Selon Alex Speder <[email protected]>: > Greetings all, > > I recently attempted to update a Java project from GDAL 1.8.1 to GDAL > 1.9. However, I noticed the statistics being computed on my output > rasters were off. After doing some digging, it seems that something > changed in the HFA driver's handling of minimum and maximum values. > IN GDAL 1.8.1 I could set a Float32 raster's NoData value to > Float.NEGATIVE_INFINITY and it would work as expected, i.e. pixels > with NoData values were ignored. This no longer appears to be the > case in GDAL 1.9. I have only seen this behavior with > Float.NEGATIVE_INFINITY or Float.POSITIVE_INFINITY as the NoData > (although with positive infinity the problem is reversed). Is this > the intended behavior?
No, this is a regression. I've created ticket http://trac.osgeo.org/gdal/ticket/4506 and pushed a fix (as well a new regression test for that use case). Thanks for your report. _______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev
