Opened 12 years ago

Closed 11 years ago

Last modified 9 years ago

#9686 closed (fixed)

GeoDjango should support the sqlite3 back end via SpatiaLite

Reported by: mdh Owned by: jbronn
Component: GIS Version: 1.0
Severity: Keywords:
Cc: Triage Stage: Accepted
Has patch: yes Needs documentation: yes
Needs tests: no Patch needs improvement: yes
Easy pickings: no UI/UX: no


GeoDjango should support the sqlite3 back end via SpatiaLite. I've been working on this for a bit, and it mostly works, so I'm uploading my latest code so that other folks can take a look, comment, and help out.

In addition to this patch you will need these things:

  • A reasonably modern version of SQLite3. Definitely at least version 3.3.7. I'm using version 3.6.4. Run “sqlite3 --version” to check yours.
  • At least version 2.5.0 of pysqlite2. Run “python -c "from pysqlite2 import dbapi2 ; print dbapi2.version"” to check yours.
  • Some version of SpatiaLite. I use 3.6.2. Run “spatialite --version” to check yours.
  • The latest patch from ticket #6064, to let GeoDjango initialize SpatiaLite when the connection is opened.
  • The latest patch from ticket #9628, to let Django use your pysqlite2 module instead of the built-in sqlite3 module.
  • The latest patch from ticket #9633, to let the SpatiaLiteAdaptor class work. (We may be able to do away with this somehow.)

Right now, unless you're using a test database within the Django testing framework, you will need to initialize your geospatial database yourself. All the code to do it is there for the testing framework, though. This could be done entirely automagically, or it could be done with a special management command. I'm usually not a fan of magic, but in this case the whole point is to make it as trivial to get started with GeoDjango as it is to get started with the rest of Django, so I'm more open to a little bit of it.

Anyway! Let me know if you play with this!

Attachments (1)

9686-spatialite-back-end-for-geodjango.diff (36.7 KB) - added by mdh 12 years ago.
A first attempt at supporting a SpatiaLite back end for GeoDjango

Download all attachments as: .zip

Change History (9)

Changed 12 years ago by mdh

A first attempt at supporting a SpatiaLite back end for GeoDjango

comment:1 Changed 12 years ago by mdh

Component: UncategorizedGIS

Okay, in order to overcome’s upload file size limitation and create a more readable patch, I ended up removing four data files from the patch. So, in addition to the patch itself, you will need to unpack this tarball into your Django repository in order for the geospatial database initialization and tests to work properly:

comment:2 Changed 12 years ago by mdh

Needs documentation: set
Patch needs improvement: set

I'm just going ahead and marking this preemptively, because lord knows this patch needs improvement.

comment:3 Changed 12 years ago by jbronn

Owner: changed from nobody to jbronn
Status: newassigned

comment:4 Changed 11 years ago by Jacob

Triage Stage: UnreviewedAccepted

comment:5 Changed 11 years ago by jbronn

milestone: 1.1

comment:6 Changed 11 years ago by jbronn

(In [10197]) Refactored and cleaned up parts of the spatial database backend. Changes include:

  • Laid foundations for SpatiaLite support in GeoQuerySet, GeoWhereNode and the tests.
  • Added the Collect aggregate for PostGIS (still needs tests).
  • Oracle now goes to 11.
  • The backend-specific SpatialRefSys and GeometryColumns models are now attributes of SpatialBackend.
  • Renamed GeometryField attributes to be public that were private (e.g., _srid -> srid and _geom -> geom_type).
  • Renamed create_test_db to create_test_spatial_db.
  • Removed the legacy classes GeoMixin and GeoQ.
  • Removed evil \ from spatial backend fields.
  • Moved shapefile data from tests/layermap to tests/data.

Fixed #9794. Refs #9686.

comment:7 Changed 11 years ago by Alex Gaynor

Resolution: fixed
Status: assignedclosed

Fixed in r10222

comment:8 Changed 9 years ago by Jacob

milestone: 1.1

Milestone 1.1 deleted

Note: See TracTickets for help on using tickets.
Back to Top