Add data_queries metadata to /collections and /collections/{collection_id} endpoint #1151
+132
−3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
The Collections requirement class has Requirement 48 /req/edr/rc-common-query-type, which states how the data_queries proptery of a collection object should look.
The output formats and crs details supported by an EDR query are specified through the application configuration, loaded by the provider plugin which provides this metadata when generating the collections metadata.
There are a few query types with additional requirements, which are also implemented here:
Related Issue / Discussion
#1150
Additional Information
The Collections Metadata Examples of the official standard shows an illustrative example of how .collections[*].data_queries supposed to look.
Contributions and Licensing
(as per https://github.com/geopython/pygeoapi/blob/master/CONTRIBUTING.md#contributions-and-licensing)