We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It should not be here. Actually the other modules does not have it and the document does not include it.
https://github.com/opengeospatial/ogcapi-common/blob/master/api_modules/subset/requirements/REQ_subset_conformance.adoc
The text was updated successfully, but these errors were encountered:
Related to #337 simplification / clean-up , discuss whether we still need to keep this:
https://github.com/opengeospatial/ogcapi-common/tree/master/api_modules
directory.
Possibly we can re-organize the OpenAPI portions of it into an openapi/ directory at the root as in Maps.
openapi/
Should we merge collections/openapi separate from 19-072/openapi (Core) at the root?
This facilitates bundling an example OpenAPI definition that includes both Part 1 and Part 2 (like we did in Processes).
Sorry, something went wrong.
cmheazel
No branches or pull requests
It should not be here. Actually the other modules does not have it and the document does not include it.
https://github.com/opengeospatial/ogcapi-common/blob/master/api_modules/subset/requirements/REQ_subset_conformance.adoc
The text was updated successfully, but these errors were encountered: