#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):
I branched off master and started integrating the raster files into the
structure with the new driver. I followed your suggestions above. The new
branch is this one:
https://github.com/geodesign/django/tree/raster/django/contrib/gis/gdal
- Moved all tests into gdal.tests folder
- Separated constants from utils functions
- Moved RasterField into `django.contrib.gis.db.models.fields` module
Most of the changes are file-rearangements.
The raster field can leverage some of the features around the
GeometryFields, but here some of the code that can be re-used is named
Geometry* for instance the GeometryProxy and the `geom_type` property.
Both are related to lazy-instanciation of field target instances (Rasters
or Geometries).
See:
https://github.com/geodesign/django/blob/raster/django/contrib/gis/db/models/fields.py#L356
https://github.com/geodesign/django/blob/raster/django/contrib/gis/db/models/fields.py#L390
--
Ticket URL: <https://code.djangoproject.com/ticket/23804#comment:9>
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.a847d47aefdc346de1f61e4510d16fbd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
