Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explore feasibility of doing GIS API using Spatialite instead of PostGIS for ridership data #28

Closed
znmeb opened this issue Mar 6, 2018 · 2 comments
Assignees
Labels

Comments

@znmeb
Copy link
Contributor

znmeb commented Mar 6, 2018

GeoDjango is capable of using Spatialite as a back end instead of PostGIS. (https://docs.djangoproject.com/en/2.0/ref/contrib/gis/install/#spatial-database). While PostGIS is preferred, our deployed application may not have a PostGIS server available, just PostgreSQL.

The ridership data is small-ish and very tidy - Spatialite should be capable of doing any GIS work GeoDjango has to do. And the Spatialite database is an SQLite database - it's just a file that lives in the same filesystem image as the container serving up the Django REST Framework API.

@znmeb
Copy link
Contributor Author

znmeb commented Mar 6, 2018

Spatialite home page: https://www.gaia-gis.it/gaia-sins/

@znmeb
Copy link
Contributor Author

znmeb commented Mar 8, 2018

Closing - so far the only Spatialite use case is the Census GDBs with the 1740-column table. Spatialite's in the data-science-pet-containers if we need it

@znmeb znmeb closed this as completed Mar 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant