It's stored on the file system. This is to improve performance when storing large geospatial datasets.
This would only work on PostGIS. On Thursday, December 15, 2016 at 3:11:37 PM UTC-5, Adam Johnson wrote: > > I can't say I'm that familiar with GeoDjango, but that does sound like a > useful feature. Where does the data get stored if not in the DB? And does > this feature exist on any of the other database backends that GeoDjango > supports? > > On 14 December 2016 at 18:40, Piero Toffanin <pier...@gmail.com > <javascript:>> wrote: > >> Hello, >> >> Not sure this is the right place to post this, if not, could somebody >> point me to the right place? >> >> I recently had the need to use GeoDjango to define a model that uses a >> RasterField to store a GeoTIFF raster. >> https://docs.djangoproject.com/en/1.10/ref/contrib/gis/model-api/#rasterfield >> >> Upon testing, one of the users of the application found that loading a >> large GeoTIFF (100Mb+) caused PostgreSQL to fail. More details about the >> report are available here: >> https://github.com/OpenDroneMap/WebODM/issues/55 >> >> I went around the problem by using a relatively new feature of PostGIS >> that allows raster files to be stored off db. I noticed that RasterField >> does not support such feature, so I wrote the code to enable support for it >> via a new OffdbRasterField ( >> https://github.com/OpenDroneMap/WebODM/blob/master/app/postgis.py). >> The from_pgraster and to_pgraster functions are modified versions of the >> same functions found here: >> https://github.com/django/django/blob/master/django/contrib/gis/db/backends/postgis/pgraster.py >> >> Just wanted to see if there was an interest in adding off db raster >> support into GeoDjango core. Perhaps by modifying RasterField to have an >> additional parameter "offdb=True|False" and implement the necessary logic? >> >> Thanks, >> >> -Piero >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django developers (Contributions to Django itself)" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to django-develop...@googlegroups.com <javascript:>. >> To post to this group, send email to django-d...@googlegroups.com >> <javascript:>. >> Visit this group at https://groups.google.com/group/django-developers. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-developers/cbcf7634-9b24-418a-9c16-9e9b7f77fa51%40googlegroups.com >> >> <https://groups.google.com/d/msgid/django-developers/cbcf7634-9b24-418a-9c16-9e9b7f77fa51%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Adam > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/5b0ba3e3-733f-4304-bacf-dfc027d64806%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
