Welcome to the CoveragesDWG web
"The WCS 2.0 XML schema set is much easier to use than the 1.x XML; it validates and is better organized"
Table of Contents
| Conformance Testing
| Coverage Data and Service Model
| Known Implementations
| WCS History
The Coverages Domain Working Group
(Coverages.DWG) is a community oriented working group of the Open Geospatial Consortium
(OGC) established for exchanging on the OGC coverage data and service standards
. Coverage data
form digital representations of space/time varying phenomena, such as regularly and irregularly gridded data, like 1-D sensor time series, 2-D satellite imagery, 3-D x/y/t image time series and geoscientific models, 4-D x/y/z/t climate and ocean data sets, but also non-gridded data like point clouds, TINs, and general meshes.
They can be served conveniently through the Web Coverage Service
(WCS) suite and the Web Coverage Processing Service
(WCPS) coverage query language.
This Twiki as well as the corresponding email list
provide a public forum for communication. Anyone can edit this wiki, but, of course, responsibly. Instructions can be found on the TWiki Text Formatting Rules
The Coverages.DWG does not directly revise OGC standards
, but rather enables collaboration and communication between groups with spatio-temporal modeling interests. See also the Temporal.DWG
which specifically addresses temporal data aspects.
The group is chaired by Peter Baumann ( Jacobs University Bremen
) and Stephan Meissl ( EOX IT Services GmbH
Coverage Data and Service Model
- Coverage data and service definition in OGC and Coverages FAQ and 15min primer video and a coverage and WCS webinars collection
- Coverage data form digital representations of space/time varying phenomena. Examples include gridded data, like 1-D sensor time series, 2-D satellite imagery, 3-D x/y/t image time series and geoscientific models, 4-D x/y/z/t climate and ocean data sets, but also non-gridded data like point clouds, TINs, and general meshes.
- Coverage services are concentrated mainly (although not exclusively) in the Web Coverage Service (WCS) suite. It provides a versatile spectrum ranging from simple access and subsetting in different formats (as per WCS Core) up to versatile server-side ad-hoc processing and filtering through the Web Coverage Processing Service (WCPS).
- WCS standards documents official location * EA UML model (for information only, not an official standard document -- this is the source for the UML diagrams in the coverage specifications; contact: Peter Baumann)
- Several publications explain and illustrate use of WCS, as well as the technological advances made with WCS 2; an introduction to coverages and WCS is kindly provided by rasdaman GmbH. Whenever writing scientific articles about coverages and WCS, do the editors a favour and cite their scientific work, following good practice - much appreciated!
- ideas for future work on coverages/GMLCOV and the WCS suite
- November 2015: Following successful presentation in the OAB, the new OGC Coverage Implementation Schema (CIS) 1.1 is now being rolled out for public comments.
- September 2015: New coverage model approved by WCS.SWG, now entering the adoption pipeline: Coverage Implementation Schema (CIS) 1.1 (backwards compatible extension to GMLCOV, renamed to better reflect contents) -- see CoveragesBigPicture
- August 2015: Enterprise Architect UML model of WCS suite uploaded
- August 2015: WCS-T passed RFC without change requests, now to be presented to TC prior to voting period
- March 2015: WCS-T 2.0 released for RFC. It adds insert, delete, and update capabilities to a server.
- September 2014:OGC Technical Meeting in Calgary:
- OGC approaches ISO TC211 to adopt OGC GMLCOV, WCS Core, and WCS POST/XML as ISO standards. JAG (Joint Advisory Group) was tasked to initiate the process.
- coverage encodings for JPEG200, GMLJP2 adopted; JPIP is on its way
- WCS-T adopted as DP
- January 2013:In OWS-9, WCS has been brought close to completion by establishing a series of specifications, Abstract Test Suites (ATSs) and Executable Test Scripts (ETSs):
- Specs added: WCS Processing Extension v2;
- ATSs added: Range Subsetting, Scaling, Interpolation, CRS, Processing, GeoTIFF;
- ETSs added: GMLCOV Corrigendum 1.0.1, WCS Core Corrigendum 2.0.1, CRS Extension, EO-WCS.
- October 2012: GeoTIFF and JPEG2000 format encodings for coverage have been released by the WCS.SWG, recommending them for public Request for Comment (RFC).
- August 2012: By vote of OGC, the WCS GET-KVP corrigendum version 1.0.1 has been accepted. It provides a slight modification necessary for the format encoding flexibility introduced with GMLCOV 1.0.1 and WCS 2.0.1.
- August 2012: The Range Subsetting Extension has been released by the WCS.SWG, recommending it for public Request for Comment (RFC).
- August 2012: the OGC Coordinate Reference System (CRS) Name Type Specification (NTS) [OGC 11-135] has been released by the WCS.SWG, recommending it for public Request for Comment (RFC) as a Best Practice Paper (available on this page); this document establishes a uniform naming system for CRS identifiers, allowing general multi-dimensional CRSs.
- July 2012: Corrigenda have been published for WCS Core and GML Application Schema - Coverages (GMLCOV).
- May 2012: rasdaman is the first WCS implementation to pass the WCS Core test suite and, therefore, becomes candidate reference implementation.
- December 2011:a proposal for OGC Name Type Specification for Coordinate Reference Systems (CRSs) has been presented, together with an open-source registry implementation. During the next weeks this resolver will be set up as a prototype service by OGC.
- EO-WCS (OGC® Web Coverage Service 2.0 Interface Standard - Earth Observation Application Profile, OGC 10-140) recommended for vote by WCS.SWG
- GeoTIFF Profile (OGC® GML Application Schema - Coverages - GeoTIFF Coverage Encoding Profile, OGC 12-100r1) ready by WCS.SWG
- WCS CRS Extension passed public Request for Comment, now under voting
- 4 WCS extension drafts ready by WCS.SWG, waiting for OGC's roll-out: WCS Range ("band") Subsetting Extension, WCS Scaling Extension, WCS Interpolation Extension, WCS Processing Extension
- WCS Application Profile MetOcean commenced
- WCS RESTful interface under finalization
- The CRS Name Type Specification is adopted by OGC, and the corresponding CRS resolver is running at OGC -- from now on, spatial, temporal, and "abstract" coordinate axes can be treated alike, and can be mixed freely (such as temporal WGS84, or CRSs for x/t and y/z slices as produced by a WCS)
- WCS: conformance tests are established and available for WCS Core, GET KVP. The following have been submitted to OGC beginning 2015 and are waiting to be published: XML/POST; SOAP; Range Subsetting; Scaling; CRS; Interpolation; Processing.
- Coverages: for GML-encoded coverages, there is a conformance tests at http://cite.opengeospatial.org/teamengine/about/gml32/3.2.1/site/ .
WCS enjoys a large and growing number of implementations, such as the following:
- open-source projects: rasdaman (WCS Core Reference Implementation), MapServer, EOxServer, GeoServer, GDAL, QGIS, OpenLayers, OPeNDAP /Hyrax, George Mason University, NASA GSFC, ESRI ArcGIS, ...
- commercial products: Envitia ChartLink, Pyxis WorldView Studio, Constellation-sdi, Pixia, ESRI ArcGIS, ...
Note that the list above is not authoritative (the page maintainers do not regularly check the links) and does not constitute any endorsement nor a statement of OGC nor anybody else about conformance. Information is provided as is, without any warranty.
WCS 2.0 has several significant advantages over previous versions: it relies on the GML coverage model, leading to increased interoperability as well as harmonization across OGC standards; among the main features are:
- extends beyond pure raster grids to support all coverage types which GML 3.2.1 knows, e.g., curvilinear grids, irregular grids, point clouds, surface coverages; general meshes;
- crisp and modular, consisting of a small mandatory core and a structured universe of optional extensions;
- harmonized with OGC OWS-Common, GML, SWE, WMS, WCPS, and WPS
- has a clear, formally specified syntax (XML Schema) and semantics (Schematron) easing understanding and implementation;
- testable: for the first time, pixel contents is subject to conformance testing. In other words: conformance of coverage data and services can be tested down to single pixel level.