maxcollombin
commented
1 year ago Hi @olivergrimm ,
Regarding the STAC endpoint of the pygeoapi service, we are currently only serving a raster file without the associated metadata. The efforts have been focused on the publication of the entire Swiss Data Cube (SDC) content as a STAC catalogue independent of pygeoapi and accessible via the links below:
STAC catalogue publication on pygeoapi is indeed possible in the following way and actually requires configuration files in addition to the associated data (*.tif files).
In addition to STAC, pygeoapi allows to publish metadata via OGC API Records.
There are currently 2 types of provider:
- ElasticsearchCatalogue
- TinyDBCatalogue
We have opted for the second possibility, which involves referencing a file in the service configuration, as you have seen. We have not exposed the data on github but to get an idea, the content of the file looks like this.
I also opened an issue to pygeoapi to integrate a CSW service as a provider (e.g. https://www.geocat.ch/geonetwork/srv/fre/csw?service=CSW&version=2.0.2&request=GetCapabilities).
I hope that I have been able to answer the question correctly and I am at your disposal for any further information.
@maxcollombin I'm currently struggling on the question where in pygeoapi in your testbed the metadata of a single item are defined? f.e.: https://ogc.heig-vd.ch/pygeoapi/stac/ndwi/NDWI_2006 In your local.config.yml I can see the metadata defs for the stac-collection, but none for the single item. Did you used yml-files beside the tif's (in that case?). Thanks for a short hint?