Closed justb4 closed 3 years ago
Let's discusse this per case / demo setup. For now, we should not make it too difficult. A postgis database for some cases is fine, as is a deployment with a Geopackage file. And proxies to WFS2 implementations I think
A data strategy should be adopted for each service, depending on the use case. Various options are discussed in docs.
Most of the OGC API services need "data" (except those that are pure proxies, e.g. for a remote WFS) in some form(at): GeoPackage, PostGIS etc. Small datasets can be maintained in GitHub but for bigger datasets and a PostGIS database we need a strategy how to manage that data. It should also be easy for maintainers to add a new dataset together with a service layer.
Some ideas how to realise data management, from simple to advanced:
Needs discussion for best option. Also what a use-case scenario would look like, also in the light of automatic deployment...