You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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.
The text was updated successfully, but these errors were encountered: