#30519: Add sanity checks to Django RasterField deserialization for rasters that
are not fully managed through Django.
------------------------------------------------+------------------------
Reporter: Daniel Wiesmann | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: GIS | Version: master
Severity: Normal | Keywords: raster
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
------------------------------------------------+------------------------
When using the RasterField for raster columns in PostGIS that are not
fully managed by Django, the raster table could be of a type that is not
supported by the GDALRaster. Examples are out-of-db rasters, or rasters
that have an unsupported pixeltype (single bit rasters, 2 or 4 bit
rasters).
A paragraph about this could be added to the documentation, and some
sanity checks could be added to the raster deserialization here:
https://github.com/django/django/blob/master/django/contrib/gis/db/backends/postgis/pgraster.py
This ticket is related to https://code.djangoproject.com/ticket/30489 and
https://github.com/django/django/pull/11381
--
Ticket URL: <https://code.djangoproject.com/ticket/30519>
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/052.55d33f0550ba31d5d786bbf06d3a0de9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
