EO-WCS Request Parameters

The following tables provide an overview over the available EO-WCS request parameters for each operation supported by EOxServer.

Please see EOxServer’s Demonstration for complete sample requests.

GetCapabilities

Table: “EO-WCS GetCapabilities Request Parameters” below lists all parameters that are available with Capabilities requests.

EO-WCS GetCapabilities Request Parameters
Parameter Description / Subparameter Allowed value(s) / Example Mandatory (M) / Optional (O)
→ service Requested service WCS M
→ request Type of request GetCapabilities M
→ version [1] Version number 2.0.1 O
→ acceptVersions [1] Prioritized sequence of one or more specification versions accepted by the client, with preferred versions listed first (first supported version will be used) version1[,version2[,...]] 2.0.1, 1.1.2, 1.0.0 O
→ sections Comma-separated unordered list of zero or more names of zero or more names of sections of service metadata document to be returned in service metadata document. Request only certain sections of Capabilities Document section1[,section2[,...]]
  • DatasetSeriesSummary
  • CoverageSummary
  • Contents
  • All
  • ServiceIdentification
  • ServiceProvider
  • OperationsMetadata
  • Languages
O
→ updateSequence Date of last issued GetCapabilities request; to receive new document only if it has changed since “2013-05-08” O

DescribeCoverage

Table: “EO-WCS DescribeCoverage Request Parameters” below lists all parameters that are available with DescribeCoverage requests.

EO-WCS DescribeCoverage Request Parameters
Parameter Description / Subparameter Allowed value(s) / Example Mandatory (M) / Optional (O)
→ service Requested service WCS M
→ request Type of request DescribeCoverage M
→ version [1] Version number 2.0.1 M
→ coverageId

NCName(s):

  • valid coverageID of a Dataset
  • valid coverageID of a StichedMosaic
  M

DescribeEOCoverageSet

Table: “EO-WCS DescribeEOCoverageSet Request Parameters” below lists all parameters that are available with DescribeEOCoverageSet requests.

EO-WCS DescribeEOCoverageSet Request Parameters
Parameter Description / Subparameter Allowed value(s) / Example Mandatory (M) / Optional (O)
→ service Requested service WCS M
→ request Type of request DescribeEOCoverageSet M
→ version [1] Version number 2.0.1 M
→ eoId

Valid eoId:

  • using the coverageId of a Datatset
  • using the eoId of a DatatsetSeries
  • using the coverageId of a StitchedMosaic
  M
→ subset

Allows to constrain the request in each dimensions and define how these parameters are applied.

The spatial constraint is expressed in WGS84, the temporal constraint in ISO 8601.

Spatial trimming: Name of an coverage axis (Long or Lat) Temporal trimming: phenomenonTime Plus optional either:

  • containment = overlaps (default)
  • containment = contains

Any combination thereof (but each value only once per request)

  • Lat,http://www.opengis.net/def/ crs/EPSG/0/4326(32,47)
  • Long,http://www.opengis.net/def/ crs/EPSG/0/4326(11,33)&
  • phenomenonTime(“2006-08-01”, “2006-08-22T09:22:00Z”)
  • Lat,http://www.opengis.net/def/ crs/EPSG/0/4326(32,47)& Long,http://www.opengis.net/def/ crs/EPSG/0/4326(11,33)& phenomenonTime(“2006-08-01”, “2006-08-22T09:22:00Z”)& containment=contains
O
→ containment see subset parameter
  • overlaps (default)
  • contains
O
→ section see GetCapabilities
  • DatasetSeriesSummary
  • CoverageSummary
  • All
O
→ count Limits the maximum number of DatasetDescriptions returned in the EOCoverageSetDescription. 10 O

GetCoverage

Table: “EO-WCS GetCoverage Request Parameters” below lists all parameters that are available with GetCoverage requests.

EO-WCS GetCoverage Request Parameters
Parameter Description / Subparameter Allowed value(s) / Example Mandatory (M) / Optional (O)
→ service Requested service WCS M
→ request Type of request GetCoverage M
→ version [1] Version number 2.0.1 M
→ coverageId

NCName(s):

  • valid coverageID of a Dataset
  • valid coverageID of a StichedMosaic
  M
→ format

Requested format of coverage to be returned, currently:

  • image/tiff
  • image/jpeg
  • image/png
  • image/gif
image/tiff M
→ mediatype

Coverage delivered directly as image file or enclosed in GML structure

  • not present or
  • multipart/mixed
multipart/mixed O
→ subset

Trimming of coverage dimension (no slicing allowed!)

  • the label of a coverage axis
    • plus either:
      • pixel coordinates
      • without CRS (→ original projection)
      • with CRS (→ reprojecting)
  • x(400,200)
  • Lat(12,14)
  • Long,http://www.opengis.net/def/ crs/EPSG/0/4326(17,17.4)
O
→ rangesubset Subsetting in the range domain (e.g. Band-Subsetting).
  • 1,2,3
  • Blue,Green,Red
O
→ outputcrs

CRS for the requested output coverage

  • not present or
  • CRS
http://www.opengis.net/def/crs/ EPSG/0/3035 O
  • → size or
  • → resolution

Mutually exclusive per axis, either:

  • integer dimension of the requested coverage (per axis)
  • resolution of one pixel (per axis)
  • size=Long(20)
  • size=x(50)
  • resolution=long(0.01)
  • resolution=y(0.3)
O
→ interpolation [2]

Interpolation method to be used

  • nearest (default)
  • bilinear
  • average
bilinear O
→ mask [3]

Masking of coverage

  • by polygon
    • define the polygon by a list of points (i.e. latitude and longitude values), e.g. lat1,lon1,lat2,lon2,...
    • make sure to close the polygon with the last pair of coordinates
    • providing the polygon CRS is optional; per default EPSG 4316 is assumed
    • use the subset parameter to crop the resulting coverage
  • by coverage(s) (not implemented yet)
  • polygon,http://www.opengis.net/ def/crs/EPSG/0/4326(42,10,43, 12,39,13,38,9,42,10)
  • coverage(other_coverage)
O

[1](1, 2, 3, 4, 5) Version, acceptVersions: Support for EO-WCS is available only together with WCS version 2.0.1.
[2]Interpolation: (Note: Resampling options other than NEAREST can dramatically slow down raster processing). The default (and fastest) is NEAREST. Replaces the target pixel with its NEAREST Neighbor. AVERAGE will compute the average pixel value of all pixels in the region of the disk file being mapped to the output pixel (or possibly just a sampling of them). Generally AVERAGE can be desirable for reducing noise in dramatically downsampled data, and can give something approximating anti-aliasing for black and white linework. BILINEAR will compute a linear interpolation of the four pixels around the target location. BILINEAR can be helpful when oversampling data to give a smooth appearance.
[3]Please note that this is parameter is not yet OGC standardized.