search

opengeospatial / ogcapi-coverages

OGC API - Coverages draft specification
https://ogcapi.ogc.org/coverages
Apache License 2.0
22 stars 13 forks source link

Determine implications of OGC API - Common - Part 2 #64

Closed ghobona closed 3 years ago

ghobona commented 4 years ago

The SWG today (2020-05-27) discussed whether the development of OGC API - Common - Part 2: Collections might have implications for OGC API - Coverages. The SWG agreed to revise the document, if possible, to be consistent with OGC API - Common - Part 2: Collections.

jerstlouis commented 4 years ago

@pebau OGC API - Common extent defines "spatial" for WGS84, and "temporal" (both instant and intervals). It is also extensible. So we could for example define a property called "coverage-axes", which maps to all other dimensions which could not be described, and this can follow the traditional "envelope" approach for those.

Would you have an envelope example of a very complex coverage with space, time and additional dimensions, that I could use as a basis for an example to illustrate on how to encode it?

As for specifications, I have been working on them all day yesterday and all night and still now to try present something at our meeting today :)

pebau commented 4 years ago

@jerstlouis re example, here is the canonical example collection: http://schemas.opengis.net/cis/1.1/gml/examples-1.1/ Maybe most interesting are the "non-standard" cases, ie 1D time, Index CRS, 4D, etc. as opposed to 2D Lat/Long.

jerstlouis commented 4 years ago

I submitted Pull Request https://github.com/opengeospatial/ogc_api_coverages/pull/76 to try to update the standard to reflect these changes, and address other issues in the draft as well (removed unnecesary concept of a default encoding, reorganized conformance classes, addressed some media type issues). To some extent it is still work in progress. I included an itemized summary of the changes in the PR comment.

Schpidi commented 4 years ago

20200902: Coverages SWG call: Embedding vs. referencing of DomainSet and RangeType. It was decided to recommend to Common to explicitly allow relative links in the same document in the href element like "href": "#domainSet". This way we would make the link mandatory which could be a relative link in the same document.

jerstlouis commented 4 years ago

PR https://github.com/opengeospatial/ogc_api_coverages/pull/87 should address the last remaining aspects of this issues.

Schpidi commented 3 years ago

20200909: Coverages SWG call: PR #87 was merged and it was agreed to close this issue.