Skip to content
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

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

constantinius
Copy link

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 with rangetype=... etc. parameters added.

For the rangeset only it details the usage of parameters for GeoTIFF encoding taken from the GeoTIFF encoding specification.

Copy link
Contributor

@pebau pebau left a 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?

@Schpidi Schpidi added this to Backlog in Core release Nov 27, 2019
@Schpidi Schpidi moved this from Backlog to In Progress in Core release Sep 14, 2020
@Schpidi Schpidi self-assigned this Sep 14, 2020
@Schpidi
Copy link
Member

Schpidi commented Sep 23, 2020

20200923: Coverages SWG call: Document this in the Users Guide rather than the specification itself.

@Schpidi
Copy link
Member

Schpidi commented Oct 14, 2020

@Schpidi
Copy link
Member

Schpidi commented Oct 14, 2020

maybe we need to use the ;q= parameter to define accept-params as defined in RFC7231 https://tools.ietf.org/html/rfc7231#section-5.3

@Schpidi Schpidi removed this from In Progress in Core release Jan 13, 2021
@Schpidi
Copy link
Member

Schpidi commented Jan 13, 2021

related to opengeospatial/ogcapi-common#8

@Schpidi
Copy link
Member

Schpidi commented Apr 7, 2021

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/)

@KathiSchleidt
Copy link

As related to conneg by profile, latest news seems to be at: opengeospatial/ogcapi-common#8 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants