Skip to content

Decisions

Jump to bottom
Stephan Meißl edited this page Jun 10, 2020 · 6 revisions

This page captures decisions that have been taken by the WCS.SWG while working on the specification.

Formal votes

  • Motion to make the current OGC API Coverages GitHub repository (https://github.com/opengeospatial/ogc_api_coverages) public. Moved: Chuck Heazel, Seconded: Peter Baumann Passed with no objection to unanimous consent

  • Motion to capture Peter's concern in authoritative manner in the README.md of the ogc_api_coverages GitHub repository to clearly and concisely write down the scope of the work done in this repository. Moved: Chuck Heazel, Seconded: Stephan Meißl Passed with no objection to unanimous consent

  • 20191120: It is proposed to the WCS.SWG to adopt the resource path /collections/{collectionId}/coverage and drop the plural version.

    • Discussion: There is a proposal to have more concrete resource types like rectifiedGridCoverage in addition to coverage in the path.
    • Moved: Joan Maso
    • Second: Peter Baumann, Steve Olson
    • NOTUC

Decisions during meetings

  • 20190412: Use YAML rather than JSON for OpenAPI definitions
  • 20190426: Base on previous work (#2)
    • D004 Swath Coverages (from TB-14)
    • WCS Core 2.1: 17-089r1
    • Coverages Implementation Schema 1.1: 09-146r6
    • Web Query Service (WQS): 14-121
    • URL templates (RFC 6570) whenever possible
  • 20190503: Filtering / Subsetting (#16): Support both methods (bbox and subset) in filtering on collection level but only use subset mechanism on coverage level
  • 20200610: As discussed it is decided to follow the precedence of OGC API - Features: Part 1 - Core to not make any particular format mandatory but only make a recommendation for CIS JSON, CIS RDF, GeoTIFF, netCDF, and CoverageJSON. Each format needs it's separate conformance class.
  • 20200610: Path restructuring
    • Merge current "coverage offering" ({collectionID}/coverage) directly into {collectionID}, e.g. envelope property, and links and/or properties for the coverage description
    • Get rid of {collectionID}/coverage/description (integrated in {collectionID})
    • Get rid of {collectionID}/coverage/all (now returned by /coverage)
    • Get rid of {collectionID}/coverage/rangetype (always a property in {collectionID}, following CIS JSON encoding)
    • Make {collectionID}/coverage/domainset optional (Can either be a property in {collectionID}, or a link in the case of complex domainset, which may also support subsetting) -- NOTE: Either a property or a link is still required, and always encoded as CIS JSON, though in the case of a link it could additionally be provided in other formats.
    • Make {collectionID}/coverage/rangeset optional (only present when format supports providing the rangeset without the description, i.e. a raw naked set of values)
    • Make {collectionID}/coverage/metadata optional, linked from {collectionID}
    • Result
      • coverageid should be understood synonymous to collectionid
      • GET /collections/{coverageid} - including description, rangeType, and domainSet (at least as link)
      • GET /collections/{coverageid}/coverage - the whole coverage
      • GET /collections/{coverageid}/coverage/metadata - optional
      • GET /collections/{coverageid}/coverage/rangeset - optional
      • GET /collections/{coverageid}/coverage/domainset - optional
      • GET /collections/{coverageid}/coverage/rangetype - optional
Clone this wiki locally