#26592: Add support for GDAL 2.1
-----------------------------+------------------------------------
Reporter: yellowcap | Owner: nobody
Type: New feature | Status: new
Component: GIS | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+------------------------------------
Comment (by yellowcap):
For empty bands, the statistics computation raises a GDALError. Before
GDAL 2.1, the function returned null values. In 2.1 the input c_double
values remain unchanged, so there is not way to know if the values are
true values when the default is returned. Therefore try/except might be
necessary. This is what is implemented in the current pull request.
An alternative would be to write a custom error-checking function in the
gdal errcheck module for this case.
https://github.com/django/django/blob/master/django/contrib/gis/gdal/prototypes/errcheck.py
Please advise on what makes more sense architecture-wise.
--
Ticket URL: <https://code.djangoproject.com/ticket/26592#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.d538e4cff92a58b408d5cb07b86f3508%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
