#25734: Nodata value not excluded when computing GDALBand min/max values
-------------------------------------+-------------------------------------
Reporter: yellowcap | Owner: nobody
Type: Bug | Status: closed
Component: GIS | Version: 1.8
Severity: Normal | Resolution: fixed
Keywords: raster gdal gis | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"8f5904560a7ab51d480410ca5228df1a28ec2295" 8f59045]:
{{{
#!CommitTicketReference repository=""
revision="8f5904560a7ab51d480410ca5228df1a28ec2295"
Fixed #25734 -- Made GDALBand min and max properties use
GDALComputeRasterStatistics.
Thanks Sergey Fedoseev and Tim Graham for the review.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/25734#comment:5>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.b2d38390763dbc5d4bc9481cb5fc5df2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
