id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
25734	Nodata value not excluded when computing GDALBand min/max values	Daniel Wiesmann	nobody	"The `min` and `max` properties of `GDALBand` objects only return the ""true"" min or max value when the underlying band has statistics calculated, otherwise they return the min/max of the datatype will be returned.

This is expected behavior of the gdal C function but should be different for the GDALBand properties. The property should return the true min/max.

http://www.gdal.org/classGDALRasterBand.html#aaabf419931d0f505428f91cff54085cc

The propsed solution for this is to add the ""GDALComputeRasterStatistics"" function to the prototypes and use that instead of the ""GDALGetRasterMinimum/Maximum""  functions.

http://www.gdal.org/gdal_8h.html#aa93b6b6ea6e71017ce25524e1a9ef1e3"	Bug	closed	GIS	1.8	Normal	fixed	raster gdal gis	Baptiste Mispelon	Ready for checkin	1	0	0	0	0	0