-
-
Notifications
You must be signed in to change notification settings - Fork 261
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe required collection level metadata about EDR Queries #1744
Conversation
Pausing until opengeospatial/ogcapi-environmental-data-retrieval#563 is addressed. |
+1 I am interested in clarifying the |
OGC API - Features does not imply a temporal model for collections. Feature data may or may not have a temporal aspect. OGC API - Environmental Data Retrieval implies a more specific collection model given the temporal nature of the data it aims to support. |
As written, there is no differentiation between the OGC API - EDR and OGC API - Features temporal configuration. Should EDR collections be validated against https://schemas.opengis.net/ogcapi/edr/1.1/openapi/schemas/collections/extent.yaml? Or is it fine as implemented in this PR? |
pygeoapi only validates OpenAPI generation and config (not at runtime). For responses, we create the response as per the specification(s) and leave hard validation to CITE. |
Update schema definition to match https://schemas.opengis.net/ogcapi/edr/1.1/openapi/schemas/collections/extent.yaml
…to edr-context
Overview
Adds the necessary components to decribe EDR collections to work with EDR clients like
https://labs.metoffice.gov.uk/edr/static/html/query.html
Related Issue / discussion
#1151
Additional information
Demo running on this branch
Dependency policy (RFC2)
Updates to public demo
Contributions and licensing
(as per https://github.com/geopython/pygeoapi/blob/master/CONTRIBUTING.md#contributions-and-licensing)