#25734: Nodata value not excluded when computing GDALBand min/max values
----------------------------+-----------------------------
Reporter: yellowcap | Owner: nobody
Type: Bug | Status: new
Component: GIS | Version: 1.8
Severity: Normal | Keywords: raster gdal gis
Triage Stage: Unreviewed | Has patch: 1
Easy pickings: 0 | UI/UX: 0
----------------------------+-----------------------------
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
--
Ticket URL: <https://code.djangoproject.com/ticket/25734>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/052.cd66d6dfca59c77c9732485043b36c05%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
