Tom Kralidis

As discussed, an initial iteration could be listing/access of styles via `/styles`. Future iterations would include association of a style to a resource and transaction interfaces.

Catching up here, as @doublebyte1 mentions, we have styles in a couple of contexts. Below are thoughts on workflows: 1. OGC API - Styles support: this means listing/fetching styles from...

@frafra any update on this PR?

Closing this PR for now. Please feel free to re-open once it is ready for review.

Untested: ```diff diff --git a/pygeoapi/api/__init__.py b/pygeoapi/api/__init__.py index 7ce3ec4..854d667 100644 --- a/pygeoapi/api/__init__.py +++ b/pygeoapi/api/__init__.py @@ -339,7 +339,7 @@ class APIRequest: h = headers.get('accept', headers.get('Accept', '')).strip() # noqa (fmts, mimes) = zip(*FORMAT_TYPES.items())...

Thinking out loud: one approach could be to add the appropriate binding information to the `links` column in pycsw (which is a JSON) when ingesting an ISO document and then...

Thanks @pvgenuchten. Suggest that the internal model of this object be modelled after https://github.com/opengeospatial/ogcapi-records/blob/master/core/openapi/schemas/party.yaml as a rule. This would mean: - all contacts populated to `pycsw:Contacts` would be OARec compliant...

+1 for a community theme. In terms of updating in pygeoapi proper, we would need to consider CoverageJSON support as well (not sure if OL supports). Having said this, we...

pygeoapi feature/record backend providers support a [`get_schema`](https://github.com/geopython/pygeoapi/blob/master/pygeoapi/provider/base.py#L90) function, which does exactly this. However, there is no pygeoapi endpoint implemented to expose this (note that it is used by downstream applications)....

We will review our STAC support as part of the next release.