Opened 5 days ago
Last modified 33 hours ago
#36196 assigned New feature
django.contrib.gis.GDALRaster support for driver configuration options — at Initial Version
| Reported by: | Jordi Castells | Owned by: | |
|---|---|---|---|
| Component: | GIS | Version: | 5.1 |
| Severity: | Normal | Keywords: | |
| Cc: | Jordi Castells, Daniel Wiesmann, Mariusz Felisiak | Triage Stage: | Accepted |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Some raster files will refuse to open when using newer versions of GDAL (for example 3.8).
GDAL behaves as expected, although it is not always as desired. It brought to my attention that there is no support for driver specific open options when calling contrib.gis.GDALRaster
There is driver option support via papsz_options when creating GDALRaster from scratch (https://docs.djangoproject.com/en/5.1/ref/contrib/gis/gdal/#creating-rasters-from-data) but not when opening an existing raster file (https://docs.djangoproject.com/en/5.1/ref/contrib/gis/gdal/#gdalraster).
The example that I can come up now is opening a COG directly with contrib.gis.GDALRaster and requiring the option IGNORE_COG_LAYOUT_BREAK, but I imagine that other drivers would benefit from this capability.