-
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
WiP: Coverage/metadata encoding #22
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
makes all much sense to me. Just wonder whether this is too complex for the core functionality. And the metadata, as their content by definition is opaque, can likely not be recoded into anything else as the server lacks knowledge about it?
20200923: Coverages SWG call: Document this in the Users Guide rather than the specification itself. |
in support of the PR https://www.w3.org/Protocols/rfc1341/4_Content-Type.html |
maybe we need to use the |
related to opengeospatial/ogcapi-common#8 |
monitor the proposal for "Content Negotiation by Profile" https://www.w3.org/TR/dx-prof-conneg/ (see https://mailarchive.ietf.org/arch/msg/httpapi/gNW6BBxaQSsjtKHuTFwTkIld7L8/) |
As related to conneg by profile, latest news seems to be at: opengeospatial/ogcapi-common#8 (comment) |
Work in progress! Will be discussed on the hackathon.
This PR adds information about how to encode coverages and/or parts thereof.
For a complete coverage, the use of
multipart/related
withrangetype=...
etc. parameters added.For the rangeset only it details the usage of parameters for GeoTIFF encoding taken from the GeoTIFF encoding specification.