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

do not enforce multipart #20

Closed
pebau opened this issue May 3, 2019 · 1 comment
Closed

do not enforce multipart #20

pebau opened this issue May 3, 2019 · 1 comment

Comments

@pebau
Copy link
Contributor

pebau commented May 3, 2019

Req 2.3 says: "A coverage accessed according to requirement 2.2 SHALL be returned as multipart coverage including the DomainSet, RangeType, and RangeSet in the coverage’s Native Format."

Multipart is just one possible encoding, others have their practical relevance (and importance) as well. Also, coverage components enumerated are incomplete. Further, demanding Native Format is contradicting format negotiation.

AFAICS what this req wants to say is: coverage shall be encoded according to the format negotiation - this, however, is already stated elsewhere.

What is open is the (coverage specific) distinction of single-file vs multipart; se WCS 2.0 for its definition.

Bottom line, rather than reinventing a description hastily we might want to rely on CIS 1.1 which defines it. Hence, suggestion:

"A coverage SHALL be returned encoded as defined in OGC CIS 1.1 and WCS 2.0".

@Schpidi
Copy link
Member

Schpidi commented May 3, 2019

Teleconference 20190503: Make sure to add examples and explanations in informative part to not make developers need to read CIS and WCS standards.

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

No branches or pull requests

2 participants