Design interaction between GIS datasets and GeoServer

[selimnairb]

This deals with dataflow between our models, GIS datasets, and GeoServer

[selimnairb]

This includes designing GI Database data model and REST API to support this.

[selimnairb]

We can store vector and raster data in PostGIS via Django, then give GeoServer access to the data stored in PostGIS. The ingest can be handled on the Django side (e.g. through the admin console for now). Then we can, for now, manually update GeoServer to expose the data as layers for visualization. Eventually we can use GeoServer's REST API to automate this, which will be required when allowing users to provide their own data. However, until we add user accounts and permissions to the system, we don't have a good way to manage user-contributed data, so we will simplify and leave this out for now.

Raster support for Django

django-raster for reading and writing raster. Another option for querying raster data from PostGIS via Django by hand.

[selimnairb]

Need to add to bird view editor a way to generate and import geospatial (i.e. raster) data output from previous scenario runs. The use case here is if you are doing iterative design, you might want to see an output from a previous scenario (i.e. number of days saturated) when developing a new version of a previous scenario.