Page History

...

• Reach-Out - current status and planning
  • Near-Term WCS Framework for EOSDIS data
  • Near-Future Requirements - Shape-Polygon subsetting, Asynchronous behavior
  • Longer Term Plans
• Near-Term Decision Points
  (Identification and Agreement on MVP)
  • Compatible Service Requirements
    - allowing a URL Reference service to generate WCS Service call URLs given CMR search results, i.e., in support of EDSC
    
    • WCS 2.0.1(WCS 1.1.0 also?)
    • GetCoverage only
    • Coverage=Granules only - Re. CoverageID and returned data
      • CoverageID = <CMR Granule Concept ID>-- e.g. G123456789
        • With or without Preceding CollectionID?
           (e.g., Collection <CollectionID>:<GranuleID>)
          - Collection Concept ID  or  Shortname-VersionID?
      • Stitching, Granule-Agnostic , & Variable-Specific results TBD-> TBD
    • Basic WCS Synchronous behavior (at least - asynchronous is a near-future issue)
      • "Streaming" of results by default
      • "Staging" of results if '&Store=true' is specified - xml is returned with URL to access results
    • Including (as appropriate per collection)
      • Subsetting - Variable, Spatial, Temporal
        • subset=lat(20,30)&subset=lon(-150,-130)
        • subset=time(2019-01-02T01:22:42,2019-01-15T12:15:31)
        • rangesubset=/ATL03/gt1l/heights/h_ph
      • (Minor technical issue - WCS defines subsetting along dimensions of the origin data product, while we consider subsetting in spatial and temporal terms that usually have to be translated to dimensional constraints on the data product.In practice, and in most cases, I don’t think this matters, but there might be some issues along the way).
      • Shape-Polygon subsetting is a near-term requirement, but this is not in WCS standard yet
      • Reprojection, Resample
        • outputcrs=<URL> e.g. http://www.opengis.net/def/crs/EPSG/0/4326
        • scalesize=<axis(resolution)>
        • scaleextent=<axis(min, max)>-- only in rare special cases,hdf otherwise implicit in origin or subset extents
      • Format Options
        • GeoTIFF, NetCDF-4?, ESRI-Shapefile (Vector)?, ASCII (Tabular-ASCII)?
  • UMM-S Entries
  • EDSC Updates
  • Service Bridge Functionality
• Near-Future Path
• Asynchronous behavior - see Asynchronous WCS - Mapping to EOSDIS Data Services
• Shape-Polygon - see WCS and Requesting Data Within a Polygon Bounding Shape
• Asynchronous behavior
• Longer-Term
  • Stitching, Granule-Agnostic, Variable-Specific results
  • Within WCS Server - Only GetCoverage is assumed, for now,
    i.
e., EOSDIS Framework does not depend upon GetCapability/DescribeCoverage but…
    • Is GetCapability a CMR or service feature?
    • Is DescribeCoverage a CMR or service feature?
    • Is there a role for GetCapability/DescribeCoverage, when provided by service, in supporting CMR/EDSC/Service Bridge?

...

• Complicated protocol and xml schema required for implementation
• Not very restful
  e.g. - GET example.com/service?SERVICE=WCS&VERSION=1.0.0&REQUEST=GetCoverage
         - Instead of  GET example.com/service/wcs/1.0.0/coverage?
• No clear definition of coverage re. collection, granule, variable
  • granule is coverage vs granule agnostic access to science data
• No Asynchronous behavior (yet)
• Support for in-place staging of results is limited (&store=true)

• No support for subset by polygon / Shapefile (yet)

• GetCapabilities and DescribeCapabilities do not scale well
  (but perhaps we don't implement at first...)

...