#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 | Resolution:
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
-------------------------------------+-------------------------------------
Comment (by yellowcap):
That's right, I agree that its probably not critical. An alternative
simple way of "backporting" this would be to change the 1.8 documentation
on the min/max attributes. The documentation could state that the methods
might not return the true value if they are not already stored internally
in the raster or in a metatdata file. However I am not sure if that would
be good practice either.
--
Ticket URL: <https://code.djangoproject.com/ticket/25734#comment:4>
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.213e063ffb97318234ecd0438edbcc41%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
