-
Notifications
You must be signed in to change notification settings - Fork 13
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
What extensions should OAPI Coverages have? #15
Comments
Teleconference 20190426: How will this extend to application profiles? |
WCS knows about 2 types of extensions:
|
We'll have to figure out how all this applies to Application Profiles to WCS (MetOcean and EO), as well as the two type of extensions: 1) to GetCoverage and 2) extensions that include new extraction patterns (which includes the extension to the MetOcean Application Profile in the GetCorridor and GetPolygon functions) |
we might also consider extensions for the various encodings, such as:
|
The current version (12/30/19) has the following conformance classes:
|
FWIW, WCS is structured into format encodings, processing functionality, and protocol bindings. |
Have created a branch extensions with some stub contents: https://github.com/opengeospatial/ogc_api_coverages/tree/extensions/extensions, hopefully helps in discussion. |
In the WCS SWG Teleconference @cmheazel volunteered to make sure the core/extension structures like directories, Readme, etc. are aligned between common, features, and coverages. |
OBE - the process for managing extensions has matured since this issue was written. |
In addition to the Core functionality, at some time a wider range of operations should be supported, such as further subsetting, scaling, etc. Here a first attempt:
Items marked with a "+" are of relevance beyond coverage world and might be discussed in a wider context.
The text was updated successfully, but these errors were encountered: