Geographic information needed by the SCIP frontend (accessed via the SCIP backend).
There are two types of geographic entity in this database:
regions have a name, a boundary, a four letter code, and optionally an outlet point representing the most downstream point in the region. They are intended to represent various types of area a user can express interest in and see streamflow and climate projections for. Currently we support "watersheds" (as defined by the BC Freshwater Atlas) and "basins" (grouping all watersheds along a specific river) as kinds of region, but we anticipate there being more someday.
conservation_units also have a name, a boundary, a four-letter code, and optionally an outlet, but they are additionally associated with one or more salmon populations.
I have a rough shapefile-indexing script, but I will delay to the next PR; for now, I want to get the ORM into github and relased, because the SCIP-backend uses it.
Geographic information needed by the SCIP frontend (accessed via the SCIP backend).
There are two types of geographic entity in this database:
regions have a name, a boundary, a four letter code, and optionally an outlet point representing the most downstream point in the region. They are intended to represent various types of area a user can express interest in and see streamflow and climate projections for. Currently we support "watersheds" (as defined by the BC Freshwater Atlas) and "basins" (grouping all watersheds along a specific river) as kinds of region, but we anticipate there being more someday.conservation_unitsalso have a name, a boundary, a four-letter code, and optionally an outlet, but they are additionally associated with one or more salmonpopulations.I have a rough shapefile-indexing script, but I will delay to the next PR; for now, I want to get the ORM into github and relased, because the SCIP-backend uses it.