Opened 5 years ago
Last modified 2 years ago
#30519 new Cleanup/optimization
Add sanity checks to Django RasterField deserialization for rasters that are not fully managed through Django.
| Reported by: | Daniel Wiesmann | Owned by: | nobody |
|---|---|---|---|
| Component: | GIS | Version: | dev |
| Severity: | Normal | Keywords: | raster |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
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
Note:
See TracTickets
for help on using tickets.