Make coverage metadata available under the coverage/metadata path

[metmikel]

Is your feature request related to a problem? Please describe. The draft standard OGC API - Coverages - Part 1: Core seems to specify that application specific metadata may be available under the coverage/metadata path (http://docs.ogc.org/DRAFTS/19-087.html#coverage-metadata-clause & https://github.com/opengeospatial/ogcapi-coverages/blob/master/standard/openapi/paths/coverages-core/metadata.yaml) and as part of the response when requesting the coverage path (https://github.com/opengeospatial/ogcapi-coverages/blob/master/standard/openapi/schemas/cis/coverage-schema.yaml includes the metadata, although https://github.com/opengeospatial/ogcapi-coverages/blob/master/standard/openapi/schemas/coverages-core/coverageInfo.yaml does not). This might be related to https://github.com/geopython/pygeoapi/issues/122 - but this issue only considers coverage metadata.

Describe the solution you'd like We would like to be able to include application specific metadata relating to the coverages we are serving (for example the latest generation time of NWP model data), so would like this path to be supported. We would like the metadata content to be able to be supplied/supplemented by a coverage provider.

Describe alternatives you've considered We looked at (and are currently using) the approach used - by the _xarray provider - which adds a _meta tag to the DomainSet response - which seems completely non-standard.

[github-actions[bot]]

As per RFC4, this Issue has been inactive for 90 days. In order to manage maintenance burden, it will be automatically closed in 7 days.

[github-actions[bot]]

As per RFC4, this Issue has been closed due to there being no activity for more than 90 days.