#23804: Add a RasterField to GeoDjango
-----------------------------+-------------------------------------
Reporter: yellowcap | Owner: yellowcap
Type: New feature | Status: assigned
Component: GIS | Version: master
Severity: Normal | Resolution:
Keywords: raster gdal | 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):
The RasterField is still very minimalistic, here are some thoughts of what
is missing/could be improved:
- Integration with different db backends. Currently the raster IO is
tailored towrards PostGIS. The value passed to the db is the output of the
`wkb` property of the GDALRaster, which converts between PostGIS WKB and
GDALRaster. This seems to work in the test-databases. The db_type is fixed
to `'raster'`, which is also PostGIS specific.
- A deeper integration with the GeometryField would be beneficial. For
instance the SRID property could be shared in a master class. But this is
currently integrated into GeometryField directly. So integrating the two
would probably require a GeoField master class or so.
--
Ticket URL: <https://code.djangoproject.com/ticket/23804#comment:10>
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.be891843eb54653564fe22071c30ca98%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
