Open Geospatial Consortium |
Submission Date: 2016-08-31 |
Approval Date: 2018-01-02 |
Publication Date: 2018-10-04 |
External identifier of this OGC® document: http://www.opengis.net/doc/IS/WCS-EO-AP/1.1 |
Internal reference number of this OGC® document: 10-140r2 |
URL for this OGC® document: http://docs.opengeospatial.org/is/10-140r2/10-140r2.html |
PDF version (informative): http://docs.opengeospatial.org/is/10-140r2/10-140r2.pdf |
Version: 1.1 |
Category: OGC® Implementation Standard |
Editor: Peter Baumann, Stephan Meissl, Jinsongdi Yu |
OGC® Web Coverage Service 2.0 Interface Standard - Earth Observation Application Profile |
Copyright notice |
Copyright © 2014, 2016, 2018 Open Geospatial Consortium |
To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ |
Warning |
This document is an OGC Member approved international standard. This document is available on a royalty free, non-discriminatory basis. Recipients of this document are invited to submit, with their comments, notification of any relevant patent rights of which they are aware and to provide supporting documentation.
Document type: OGC® Standard |
Document subtype: Implementation |
Document stage: Approved |
Document language: English |
License Agreement
Permission is hereby granted by the Open Geospatial Consortium, ("Licensor"), free of charge and subject to the terms set forth below, to any person obtaining a copy of this Intellectual Property and any associated documentation, to deal in the Intellectual Property without restriction (except as set forth below), including without limitation the rights to implement, use, copy, modify, merge, publish, distribute, and/or sublicense copies of the Intellectual Property, and to permit persons to whom the Intellectual Property is furnished to do so, provided that all copyright notices on the intellectual property are retained intact and that each person to whom the Intellectual Property is furnished agrees to the terms of this Agreement.
If you modify the Intellectual Property, all copies of the modified Intellectual Property must include, in addition to the above copyright notice, a notice that the Intellectual Property includes modifications that have not been approved or adopted by LICENSOR.
THIS LICENSE IS A COPYRIGHT LICENSE ONLY, AND DOES NOT CONVEY ANY RIGHTS UNDER ANY PATENTS THAT MAY BE IN FORCE ANYWHERE IN THE WORLD.
THE INTELLECTUAL PROPERTY IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS NOTICE DO NOT WARRANT THAT THE FUNCTIONS CONTAINED IN THE INTELLECTUAL PROPERTY WILL MEET YOUR REQUIREMENTS OR THAT THE OPERATION OF THE INTELLECTUAL PROPERTY WILL BE UNINTERRUPTED OR ERROR FREE. ANY USE OF THE INTELLECTUAL PROPERTY SHALL BE MADE ENTIRELY AT THE USER’S OWN RISK. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR ANY CONTRIBUTOR OF INTELLECTUAL PROPERTY RIGHTS TO THE INTELLECTUAL PROPERTY BE LIABLE FOR ANY CLAIM, OR ANY DIRECT, SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM ANY ALLEGED INFRINGEMENT OR ANY LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR UNDER ANY OTHER LEGAL THEORY, ARISING OUT OF OR IN CONNECTION WITH THE IMPLEMENTATION, USE, COMMERCIALIZATION OR PERFORMANCE OF THIS INTELLECTUAL PROPERTY.
This license is effective until terminated. You may terminate it at any time by destroying the Intellectual Property together with all copies in any form. The license will also terminate if you fail to comply with any term or condition of this Agreement. Except as provided in the following sentence, no such termination of this license shall require the termination of any third party end-user sublicense to the Intellectual Property which is in force as of the date of notice of such termination. In addition, should the Intellectual Property, or the operation of the Intellectual Property, infringe, or in LICENSOR’s sole opinion be likely to infringe, any patent, copyright, trademark or other right of a third party, you agree that LICENSOR, in its sole discretion, may terminate this license without any compensation or liability to you, your licensees or any other party. You agree upon termination of any kind to destroy or cause to be destroyed the Intellectual Property together with all copies in any form, whether held by you or by any third party.
Except as contained in this notice, the name of LICENSOR or of any other holder of a copyright in all or part of the Intellectual Property shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Intellectual Property without prior written authorization of LICENSOR or such copyright holder. LICENSOR is and shall at all times be the sole entity that may authorize you or any third party to use certification marks, trademarks or other special designations to indicate compliance with any LICENSOR standards or specifications. This Agreement is governed by the laws of the Commonwealth of Massachusetts. The application to this Agreement of the United Nations Convention on Contracts for the International Sale of Goods is hereby expressly excluded. In the event any provision of this Agreement shall be deemed unenforceable, void or invalid, such provision shall be modified so as to make it valid and enforceable, and as so modified the entire Agreement shall remain in full force and effect. No decision, action or inaction by LICENSOR shall be construed to be a waiver of any rights or remedies available to it.
- 1. Scope
- 2. Conformance
- 3. Normative references
- 4. Terms and Definitions
- 5. Conventions
- 6. EO data model
- 7. EO service model
- 8. WCS extensions
- 9. Protocol Bindings
- Annex A: Conformance Class Abstract Test Suite (Normative)
- A.1. Conformance Test Classes: eowcs & eowcs_geteocoverageset
- A.1.1. EO Metadata
- A.1.2. Footprint in EO Metadata
- A.1.3. EO Coverage
- A.1.4. EO Metadata in EO Coverage
- A.1.5. EOP Identifier in EO Metadata
- A.1.6. Footprint inside BoundedBy
- A.1.7. PhenomenonTime in EO Metadata
- A.1.8. PhenomenonTime ISO9891
- A.1.9. Range type extension
- A.1.10. Range type uom
- A.1.11. Range type name
- A.1.12. Rangeset of Coverage
- A.1.13. Dataset Structure
- A.1.14. Referenceable Stitched Mosaic-structure
- A.1.15. Rectified Stitched Mosaic-structure
- A.1.16. Composed-of in Stitched mosaic
- A.1.17. Contributing Footprint inside Footprint
- A.1.18. Contributing Footprint-pairwise-disjoint
- A.1.19. Contributing Footprint-union-of-footprints
- A.1.20. Dataset Domain Set in Set in Stitched Mosaic Domain Set
- A.1.21. Datasets in Rectified Stitched Mosaic Same Offset Vector
- A.1.22. Rectified Stitched Mosaic OffsetVector
- A.1.23. Referenceable Stitched Mosaic Domainset
- A.1.24. Temporal Validity Stitched Mosaic
- A.1.25. Datasets in Stitched Mosaic Same Rangetype
- A.1.26. Nil Values in Stitched Mosaic
- A.1.27. Range Values of Stitched Mosaic
- A.1.28. Dataset Series Structure
- A.1.29. Footprint in Dataset Series
- A.1.30. TimePeriod in DatasetSeries
- A.1.31. Metadata in DatasetSeries
- A.1.32. No circular references of Dataset Series
- A.1.33. GetCapabilities Request Sections
- A.1.34. GetCapabilities Response eowcs Conformance Class in Profile
- A.1.35. GetCapabilities Response eowcs_geteocoverageset Conformance Class in Profile
- A.1.36. GetCapabilities Response Structure
- A.1.37. GetCapabilities Response DatasetSeriesSummary
- A.1.38. GetCapabilities Response DatasetSeriesSummary no-duplicates
- A.1.39. GetCapabilities Response Coverage Summary
- A.1.40. GetCapabilities Response Coverage Summary Section
- A.1.41. GetCapabilities Response DatasetSeries Summary Section
- A.1.42. GetCapabilities Response Coverage Subtype
- A.1.43. GetCapabilities Response countDefault
- A.1.44. GetCapabilities Response pagingSupported
- A.1.45. GetCapabilities Response wcseoMetadata
- A.1.46. DescribeEOCoverageSet Response defaultPackageFormat
- A.1.47. GetCapabilities Response packageFormatSupported
- A.1.48. Describe Coverage Response EO Metadata
- A.1.49. Describe Coverage Response Coverage Subtype
- A.1.50. GetCoverage Request no Slicing
- A.1.51. GetCoverage Response Coverage Type
- A.1.52. GetCoverage Response EO Metadata
- A.1.53. GetCoverage Response EO Metadata in Stitched Mosaic
- A.1.54. GetCoverage Response Footprint in EO Metadata
- A.1.55. GetCoverage Response Lineage in EO Metadata
- A.1.56. DescribeEOCoverageSet Request Structure
- A.1.57. DescribeEOCoverageSet Request Sections
- A.1.58. DescribeEOCoverageSet Request eoId
- A.1.59. DescribeEOCoverageSet Request Containment
- A.1.60. DescribeEOCoverageSet Request Dimension
- A.1.61. DescribeEOCoverageSet Request CRS
- A.1.62. DescribeEOCoverageSet Response Structure
- A.1.63. DescribeEOCoverageSet Response EO Metadata
- A.1.64. DescribeEOCoverageSet Response EO Section CoverageDescriptions
- A.1.65. DescribeEOCoverageSet Response EO Section DatasetSeriesDescriptions
- A.1.66. DescribeEOCoverageSet Response eoId
- A.1.67. DescribeEOCoverageSet Response Referred
- A.1.68. DescribeEOCoverageSet Response Containment
- A.1.69. DescribeEOCoverageSet Response PhenomenonTime
- A.1.70. DescribeEOCoverageSet Response Trim Omitted
- A.1.71. DescribeEOCoverageSet Response Bound Omitted
- A.1.72. DescribeEOCoverageSet Response CoverageSubtype
- A.1.73. DescribeEOCoverageSet Response Count
- A.1.74. DescribeEOCoverageSet Response startIndex
- A.1.75. DescribeEOCoverageSet Response numberMatched attribute
- A.1.76. DescribeEOCoverageSet Response numberReturned attribute
- A.1.77. DescribeEOCoverageSet Response startIndex attribute
- A.1.78. DescribeEOCoverageSet Response next attribute
- A.1.79. DescribeEOCoverageSet Response previous attribute
- A.1.80. GetEOCoverageSet Request Structure
- A.1.81. GetEOCoverageSet Request eoId
- A.1.82. GetEOCoverageSet Request Containment
- A.1.83. GetEOCoverageSet Request Dimensions
- A.1.84. GetEOCoverageSet Request CRS
- A.1.85. GetEOCoverageSet Request packageFormat
- A.1.86. GetEOCoverageSet Request mediaType
- A.1.87. GetEOCoverageSet Request Format
- A.1.88. GetEOCoverageSet Request Scaling
- A.1.89. GetEOCoverageSet Request Interpolation
- A.1.90. GetEOCoverageSet Request CRSs
- A.1.91. GetEOCoverageSet Response packageFormat
- A.1.92. GetEOCoverageSet Response multipart
- A.1.93. GetEOCoverageSet Response mediaType
- A.1.94. GetEOCoverageSet Response cid
- A.1.95. GetEOCoverageSet Response Format
- A.1.96. GetEOCoverageSet Response GetCoverage Applicable
- A.1.97. GetEOCoverageSet Response eoId
- A.1.98. GetEOCoverageSet Response Referred
- A.1.99. GetEOCoverageSet Response Containment
- A.1.100. GetEOCoverageSet Response phenomenonTime
- A.1.101. GetEOCoverageSet Response Trim Omitted
- A.1.102. GetEOCoverageSet Response Bound Omitted
- A.1.103. GetEOCoverageSet Response Count
- A.1.104. GetEOCoverageSet Response startIndex
- A.1.105. GetEOCoverageSet Response numberMatched attribute
- A.1.106. GetEOCoverageSet Response numberReturned attribute
- A.1.107. GetEOCoverageSet Response startIndex attribute
- A.1.108. GetEOCoverageSet Response next attribute
- A.1.109. GetEOCoverageSet Response previous attribute
- A.1.110. GetEOCoverageSet Response applySubset
- A.1.111. GetEOCoverageSet Response Scaling
- A.1.112. GetEOCoverageSet Response Interpolation
- A.1.113. GetEOCoverageSet Response CRSs
- A.1.114. Band Subsetting
- A.1.115. Scaling
- A.1.116. Interpolation
- A.1.117. CRS
- A.1.118. Encodings
- A.1.119. Protocol-bindings
- A.2. Conformance Test Class: eowcs_get-kvp
- A.2.1. eowcs_get-kvp/Mandatory
- A.2.2. eowcs_get-kvp/Conformance Class in Profile
- A.2.3. eowcs_get-kvp/describeEOCoverageSet request
- A.2.4. eowcs_get-kvp/describeEOCoverageSet eoid
- A.2.5. eowcs_get-kvp/describeEOCoverageSet containment
- A.2.6. eowcs_get-kvp/describeEOCoverageSet count
- A.2.7. eowcs_get-kvp/describeEOCoverageSet startIndex
- A.2.8. eowcs_get-kvp/describeEOCoverageSet Subset
- A.2.9. eowcs_get-kvp/getEOCoverageSet request
- A.2.10. eowcs_get-kvp/getEOCoverageSet eoid
- A.2.11. eowcs_get-kvp/getEOCoverageSet containment
- A.2.12. eowcs_get-kvp/getEOCoverageSet count
- A.2.13. eowcs_get-kvp/getEOCoverageSet startIndex
- A.2.14. eowcs_get-kvp/getEOCoverageSet packageFormat
- A.2.15. eowcs_get-kvp/getEOCoverageSet mediaType
- A.2.16. eowcs_get-kvp/getEOCoverageSet format
- A.2.17. eowcs_get-kvp/getEOCoverageSet applySubset
- A.2.18. eowcs_get-kvp/getEOCoverageSet parameters
- A.2.19. eowcs_get-kvp/getEOCoverageSet Subset
- A.3. Conformance Test Class: eowcs_soap
- A.3.1. eowcs_soap/Mandatory
- A.3.2. eowcs_soap/Conformance Class in Profile
- A.3.3. eowcs_soap/describeEOCoverageSet Request Structure
- A.3.4. eowcs_soap/describeEOCoverageSet Response Structure
- A.3.5. eowcs_soap/describeEOCoverageSet-wsdl
- A.3.6. eowcs_soap/getEOCoverageSet Request Structure
- A.3.7. eowcs_soap/getEOCoverageSet Response Structure
- A.3.8. eowcs_soap/getEOCoverageSet-wsdl
- A.1. Conformance Test Classes: eowcs & eowcs_geteocoverageset
- Annex B: Use Case Examples (Informative)
- Annex C: Revision History
- Annex D: Bibliography
i. Abstract
The OGC Web Coverage Service (WCS) Application Profile - Earth Observation (EO- WCS) defines a profile of WCS 2.0 [OGC 09-110r4] for use on Earth Observation data.
ii. Keywords
The following are keywords to be used by search engines and document catalogues.
ogcdoc, OGC document, wcs, profile, eo, earth observation, dataset, dataset series, stitched mosaic
iii. Preface
This WCS Application Profile for Earth Observation is an OGC Implementation Standard which relies on WCS 2.0 (the Core [OGC 09-110r4] plus selected extensions), the Coverages Implementation Schema (renamed from GML Application Schema - Coverages) [OGC 09-146r2], the Earth Observation Metadata Profile of Observations and Measurements [OGC 10-157r4], and GML 3.2.1 [OGC 07-036].
This document includes four annexes; only the first annex is normative.
The OGC® Abstract Specification does not require any changes to accommodate the technical contents of this (part of this) document.
Among the topics for future development are the following items:
-
Specify usage and content of
EOWCS::Lineage
in more detail.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. The Open Geospatial Consortium shall not be held responsible for identifying any or all such patent rights.
Recipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they may be aware that might be infringed by any implementation of the standard set forth in this document, and to provide supporting documentation.
iv. Submitting organizations
The following organizations submitted this Document to the Open Geospatial Consortium (OGC):
Organization name(s)
-
Jacobs University Bremen
-
EOX IT Services GmbH
-
G.I.M. Geographic Information Management nv/sa
-
European Space Agency (ESA)
-
Spot Image
Additionally, rasdaman GmbH has made substantial contributions.
v. Submitters
All questions regarding this submission should be directed to the editor or the submitters:
Name | Affiliation |
---|---|
Peter Baumann |
Jacobs University Bremen, rasdaman GmbH |
Jinsongdi Yu |
Fuzhou University |
Stephan Meissl <stephan.meissl@eox.at> |
|
Christian Schiller |
1. Scope
This OGC WCS Application Profile - Earth Observation Interface Standard - henceforth abbreviated as: WCS Earth Observation Application Profile (EO- WCS) - defines data structures and operations which together allow retrieval of Earth Observation coverages offered by a WCS 2.0 server.
EO- WCS, defines a profile of WCS 2.0 [OGC 09-110r4] for use on Earth Observation data. An Application Profile bundles several specifications and possibly adds additional requirements on an implementation. Extra requirements can be additions (for example, Dataset Series are introduced by this specification) or constraints (for example, coverages offered are required to include EO metadata).
EO-WCS provides the following specification elements.
-
Definition of specific Earth Observation coverages (EO Coverages) which have a latitude/longitude or projected x/y spatial extent and a temporal validity extent. EO Coverages are derived from Referenceable Grid Coverages and Rectified Grid Coverages as defined in the Coverage Implementation Schema (renamed from GML Application Schema - Coverages) [OGC 09-146r2]. Each EO Coverage has an EO metadata set [OGC 10-157r4] contained in its metadata which describes the coverage on hand on a higher semantic level.
-
Definition of a hierarchy which allows to group EO Coverages suitably for an efficient retrieval:
-
Datasets as plain EO Coverages (and, hence, accessible as coverages);
-
Stitched Mosaics as homogeneous collections of spatially non-overlapping subsets of Datasets, accessible themselves as coverages; and
-
Dataset Series as collections of Stitched Mosaics, Datasets, and/or Dataset Series; Dataset Series themselves are not coverages.
-
-
Bundling of several mandatory and optional WCS extensions for EO-WCS implementations.
2. Conformance
This document establishes the following requirements and conformance classes:
-
eowcs, of URI http://www.opengis.net/spec/WCS_application-profile_earth-observation/1.1/req/eowcs, defining EO-WCS on conceptual level in Clauses 6, 7, and 8; the corresponding conformance class is eowcs, with URI http://www.opengis.net/spec/WCS_application-profile_earth-observation/1.1/conf/eowcs.
-
eowcs_geteocoverageset, of URI http://www.opengis.net/spec/WCS_application-profile_earth-observation/1.1/req/eowcs_geteocoverageset, defining the GetEOCoverageSet request of EO-WCS in Clause 7 where stated, particularly subclause 7.6; the corresponding conformance class is eowcs_geteocoverageset, with URI http://www.opengis.net/spec/WCS_application-profile_earth-observation/1.1/conf/eowcs_geteocoverageset.
-
eowcs_get-kvp, of URI http://www.opengis.net/spec/WCS_application-profile_earth-observation/1.1/req/eowcs_get-kvp, defining the GET-KVP protocol binding of EO-WCS in Subclause 9.2; the corresponding conformance class is eowcs_get-kvp, with URI http://www.opengis.net/spec/WCS_application-profile_earth-observation/1.1/conf/eowcs_get-kvp.
-
eowcs_soap, of URI http://www.opengis.net/spec/WCS_application-profile_earth-observation/1.1/req/eowcs_soap, defining the SOAP protocol binding of EO-WCS on conceptual level in Subclause 9.3; the corresponding conformance class is eowcs_soap, with URI http://www.opengis.net/spec/WCS_application-profile_earth-observation/1.1/conf/eowcs_soap.
The standardization target of all requirements and conformance classes are EO-WCS implementations (currently servers).
Requirements and conformance test URIs defined in this document are relative to http://www.opengis.net/spec/WCS_application-profile_earth-observation/1.1/.
Conformance Class Abstract Test Suite (Normative) lists the conformance tests which shall be exercised on any software artifact claiming to implement EO-WCS.
3. Normative references
This OGC WCS Application Profile - Earth Observation specification consists of the present document and an XML Schema. The complete specification is identified by OGC URI http://www.opengis.net/spec/WCS_application-profile_earth-observation/1.1, the document has OGC URI http://www.opengis.net/doc/IS/WCS_application-profile_earth-observation/1.1.
The complete specification is available for download from http://www.opengeospatial.org/standards/wcs; additionally, the XML Schema is posted online at http://schemas.opengis.net/wcs/wcseo/1.1 as part of the OGC schema repository. In the event of a discrepancy between bundled and schema repository versions of the XML Schema files, the schema repository shall be considered authoritative.
The following normative documents contain provisions that, through reference in this text, constitute provisions of this specification. For dated references, subsequent amendments to, or revisions of, any of these publications do not apply. For undated references, the latest edition of the normative document referred to applies.
OGC: OGC 06-121r9, OGC Web Services Common Standard, version 2.0, 2010
OGC: OGC 09-146r2, OGC® Coverage Implementation Schema (renamed from OGC®
GML Application Schema - Coverages), version 1.0, 2012
Conformance classes used: gml-coverage, gml, multipart, special-format
OGC: OGC 09-110r4, OGC® WCS 2.0 Interface Standard- Core: Corrigendum, version
2.0, 2012
Conformance classes used: core
OGC: OGC 11-053r1, OGC® Web Coverage Service Interface Standard - CRS Extension,
version 1.0, 2014
Conformance classes used: crs, crs-gridded-coverage
OGC: OGC 12-039, OGC® Web Coverage Service Interface Standard - Scaling Extension,
version 1.0, 2014
Conformance classes used: scaling
OGC: OGC 12-040, OGC® Web Coverage Service Interface Standard - Range Subsetting
Extension, version 1.0, 2013
Conformance classes used: record-subsetting
OGC: OGC 12-049, OGC® Web Coverage Service Interface Standard - Interpolation
Extension, version 1.0, 2014
Conformance classes used: interpolation
OGC: OGC 09-147r3, OGC® Web Coverage Service 2.0 Interface Standard - KVP Protocol
Binding Extension - Corrigendum, version 1.0, 2013
Conformance classes used: get-kvp
OGC: OGC 09-149r1, OGC® Web Coverage Service 2.0 Interface Standard - XML/SOAP
Protocol Binding Extension, version 1.0, 2010
Conformance classes used: soap
OGC: OGC 12-100r1, OGC® GML Application Schema - Coverages - GeoTIFF Coverage
Encoding Profile, version 1.0, 2014
Conformance classes used: geotiff-coverage
OGC: OGC 14-100r2, OGC® CF-netCDF 3.0 encoding using GML Coverage Application
Schema, version 2.0, 2015
Conformance classes used: CF-netCDF-1.6 GML encoding, CF-netCDF-1.6 data
format, CF-netCDF-1.6 multipart data encoding
OGC: OGC 12-108, OGC® GML Application Schema - Coverages JPEG2000 Coverage Encoding
Extension, version 1.0, 2015
Conformance classes used: jpeg2000-coverage
OGC: OGC 10-157r4, OGC® Earth Observation Metadata profile of Observations &
Measurements, version 1.1, 2016
Conformance classes used: eop, sar, opt
4. Terms and Definitions
This document uses the standard terms defined in Subclause 5.3 of [OGC 06-121r9], which is based on the ISO/IEC Directives, Part 2, Rules for the structure and drafting of International Standards. In particular, the word "shall" (not "must") is the verb form used to indicate a requirement to be strictly followed to conform to this standard.
For the purposes of this document, the following additional terms and definitions apply. An arrow "→" indicates that the following term is defined in this Clause.
4.1. Coverage
digital representation of a spatio-temporally varying phenomenon as defined in [OGC 09-146r2]
4.3. Dataset Series
collection of → EO Coverages
4.4. EO Coverage
Rectified Grid → Coverage or Referenceable Grid → Coverage having an → EO Metadata record and a WGS84 footprint
4.5. EO Metadata
→ EO Coverage’s metadata record
4.6. Stitched Mosaic
→ EO Coverage composed from subsets of one or more co-referenced → Datasets
4.7. EO Product
An EO Product contains one or more related → EO Product Datasets plus metadata and optionally auxiliary data like → EO Product Quicklooks.
4.8. EO Product Dataset
One or more files each containing one or more → EO Coverages.
4.9. EO Product Quicklook
A visual representation of a usually reduced → EO Product Dataset encoded in an image format. The → EO Product Dataset may combine different bands.
4.10. Lineage record
Data structure documenting an operation that has been applied to the → Coverage of which it is part
4.11. refers to
contains, in its → EO Metadata element as defined in [OGC 10-157r4], the → EO Metadata element
5. Conventions
5.1. UML notation
Unified Modeling Language (UML) static structure diagrams appearing in this specification are used as described in Subclause 5.2 of OGC Web Services Common [OGC 06-121r9].
5.2. Data dictionary tables
The UML model data dictionary is specified herein in a series of tables. The contents of the columns in these tables are described in Subclause 5.5 of [OGC 06-121r9]. The contents of these data dictionary tables are normative, including any table footnotes.
5.3. Namespace prefix conventions
The following namespaces are used in this document. The prefix abbreviations used constitute conventions used here, but are not normative. The namespaces to which the prefixes refer are normative, however.
Prefix | Namespace URI | Description |
---|---|---|
xsd |
XML Schema namespace |
|
ows |
OWS Common 2.0 |
|
gml |
GML 3.2.1 |
|
gmlcov |
Coverages Implementation Schema 1.0 |
|
wcs |
WCS 2.0 |
|
eop |
Earth Observation Metadata Profile of Observations and Measurements |
|
opt |
Optical Earth Observation Metadata Profile of Observations and Measurements (extension of eop) |
|
sar |
SAR Earth Observation Metadata Profile of Observations and Measurements (extension of eop) |
|
wcseo |
WCS Application Profile - Earth Observation 1.1 |
|
scal |
http://www.opengis.net/wcs/scaling/1.0 (schema uses http://www.opengis.net/WCS_service-extension_scaling/1.0) |
WCS Scaling Extension |
int |
http://www.opengis.net/wcs/interpolation/1.0 (schema uses http://www.opengis.net/WCS_service-extension_interpolation/1.0 |
WCS Interpolation Extension |
crs |
WCS CRS Extension |
|
gmd |
ISO 19139 Metadata |
|
gmi |
http://standards.iso.org/iso/19115/-2/gmi/1.0 or http://www.isotc211.org/2005/gmi |
ISO 19139-2 Metadata |
mdb |
ISO 19115-3 Metadata |
5.4. Multiple representations
When multiple representations of the same information are given in a specification document these are consistent. Should this not be the case then this is considered an error, and the XML Schema shall take precedence.
6. EO data model
6.1. Overview
This Clause 6, together with Clauses 7 and 8, establishes the EO-WCS core requirements class, eowcs as well as the eowcs_geteocoverageset one where stated, particularly subclause 7.6.
The data model of this EO-WCS centers around the data structure of an Earth
Observation coverage (EO Coverage), which is a coverage extended with EO
Metadata [OGC 10-157r4] and bound to a location on the Earth. EO Coverages are a
subtype of either GMLCOV::RectifiedGridCoverage
or
GMLCOV::ReferenceableGridCoverage.
Based on this EO Coverage concept (cf. Subclause 6.3), three main data elements are defined, as follows.
-
A Dataset is an EO Coverage, which can represent, for example, a hyperspectral 2D satellite scene or a 3D atmospheric model; cf. Subclause 6.4. A Dataset can be a Rectified Dataset or a Referenceable Dataset, depending on the type of EO Coverage it is derived from.
-
A Stitched Mosaic is a collection of EO Coverages referring to co-referenced Datasets; cf. Subclause 6.5. A Stitched Mosaic can be a Rectified Stitched Mosaic or a Referenceable Stitched Mosaic, depending on the type of EO Coverage it is derived from. A Stitched Mosaic can be interpreted (i.e. requested) as a single coverage.
-
A Dataset Series is a collection of coverages and/or Dataset Series; cf. Subclause 6.6. A Dataset Series can refer to any number of Datasets, Stitched Mosaics, and Dataset Series. A Dataset Series is not a coverage itself.
Note
|
Use Case Examples (Informative) provides Use Cases to motivate the definition of these data elements. |
Note
|
Although named Dataset Series technically speaking it is a heterogeneous grouping of coverages and/or Dataset Series and can thus be used for any other concept like an EO Product containing multiple coverages with different resolutions as well. |
Figure 1 informally symbolizes how the concepts of Dataset, Stitched Mosaic, and Dataset Series relate to each other spatio-temporally, as follows.
-
A - a Dataset with a particular validity in time.
-
B - a Stitched Mosaic; all its Datasets have a spatial extent contained in the Stitched Mosaic’s spatial extent and a timespan contained in the Stitched Mosaic’s time interval. The subsets contributing to the Stitched Mosaic do not overlap in space, but there may be empty (nil) areas.
-
C - the overall Dataset Series combining Datasets and Stitched Mosaics.
Figure 2 contains the UML diagram defining classes (types) and their correlations in the EO-WCS.
6.2. EO Metadata
Every EO Coverage contains EO Metadata, consisting of an EarthObservation record as defined in the OGC Earth Observation Metadata Profile of Observations and Measurements [OGC 10-157r4] and a lineage describing the history of operations leading to the coverage on hand.
Requirement 1 |
/req/eowcs/eo-metadata-structure |
Name | Definition | Data type | Multiplicity |
---|---|---|---|
earthObservation |
EO metadata record for this coverage object |
|
one (mandatory) |
lineage |
History record describing an operation that has been applied to this object |
|
zero or more (optional) |
Note
|
Throughout this standard, eop: and EOP:: can be substituted by opt:
and OPT:: or sar: and SAR:: , respectively, as in [OGC 10-157r4] opt and
sar are in the substitution group of eop .
|
Note
|
The lineage records are supposed to describe the history of processing steps that has led to the coverage on hand. As at the time of this writing there is no canonical format for such histories available in OGC, for the purpose of this specification no assumption is made about the contents of a lineage record, except that GetCoverage appends its request verbatim as an additional record (see Requirement 55 /req/eowcs/getCoverage-response-lineage-in-eo-metadata). |
The footprint of an EO Coverage, which contains one or more bounding polygons to describe the region of valid data more accurately than the EO Coverage’s bounding box, is mandatory as opposed to [OGC 10-157r4].
Requirement 2 |
/req/eowcs/footprint-in-eo-metadata |
Note
|
As per [OGC 10-157r4], the footprint is always given in WGS84. |
6.3. EO Coverage
6.3.1. Overview
An EO Coverage is a coverage as defined in the Coverages Implementation Schema (renamed from GML Application Schema - Coverages) [OGC 09-146r2]. EO Coverages appear in two variants:
-
Rectified EO Coverages are derived from Rectified Grid Coverage as defined in [OGC 09-146r2]; and
-
Referenceable EO Coverages are derived from Referenceable Grid Coverage as defined in [OGC 09-146r2].
Requirement 3 |
/req/eowcs/eo-coverage-structure |
Note
|
An EO Coverage can have any number of dimensions as long as it adheres to the requirements below. Particularly it needs a footprint bound to the Earth and a temporal validity. |
6.3.2. EO Metadata
An EO Coverage has an EO Metadata record associated.
Requirement 4 |
/req/eowcs/eo-metadata-in-eo-coverage |
Note
|
Besides this specific metadata element there may be further metadata elements. |
Note
|
According to the rules of GML, a xlink:href URI to an accessible element
of type EOWCS::EOMetadata can be provided instead of the element itself in any
place of the XML Schema where such a metadata record appears.
|
The EO Metadata record associated with an EO Coverage contains a back reference to the coverage.
Requirement 5 |
/req/eowcs/eop-identifier-in-eo-metadata |
Note
|
Normally, this word (i.e. NCName) acting as coverage identifier will be
the only contents of the eop:identifier string and thus both elements will be
equal.
|
6.3.3. Spatio-temporal extent
The EO Coverage’s extent of valid data is given by its EO Metadata footprint, which refines the coverage’s envelope.
Requirement 6 |
/req/eowcs/footprint-inside-boundedBy |
Note
|
By definition, the footprint is expressed in WGS84. |
An EO Coverage has a time period of validity associated.
Requirement 7 |
/req/eowcs/phenomenonTime-in-eo-metadata |
Note
|
This typically is the time period where image acquisition has taken place. |
Requirement 8 |
/req/eowcs/phenomenonTime-iso8601 |
6.3.4. Range type
The range type of an EO Coverage is extended to include further useful information for example to know how to convert stored numbers to physical properties.
Requirement 9 |
/req/eowcs/rangeTypeExtension |
Requirement 10 |
/req/eowcs/rangeType-uom |
Note
|
The data type is provided explicitly in the wcseo:rangeTypeExtension
element or implicitly via the actual coverage encoding.
|
Requirement 11 |
/req/eowcs/rangeType-name |
Note
|
Typically the two values are identical. This requirement addresses cases
where the identifier includes characters not allowed in NCName like : , @ ,
$ , % , & , / , + , , , ; , or any whitespace characters or where it
starts with a number, minus, or dot. For example an ID of gray band should
use gray for the name attribute and gray%20band for the swe:identifier
element.
|
Example: The following provides an example gmlcov:rangeType
element including
additional range type information for RGB generation on swe:DataRecord
level
as well as data conversion information on swe:Quantity
level.
<gmlcov:rangeType>
<swe:DataRecord definition="http://www.opengis.net/def/property/OGC-EO/0/opt/SpectralMode/PANCHROMATIC">
<swe:extension>
<wcseo:rangeTypeExtension>
<wcseo:RGBgenerationHint>
<wcseo:bandSequence>gray gray gray</wcseo:bandSequence>
<wcseo:intervalFrom>1 4095</wcseo:intervalFrom>
<wcseo:intervalTo>1 255</wcseo:intervalTo>
<wcseo:type>http://sweet.jpl.nasa.gov/2.3/reprMathFunction.owl#Logarithmic</wcseo:type>
</wcseo:RGBgenerationHint>
</wcseo:rangeTypeExtension>
</swe:extension>
<swe:label>Gray Channel/Band</swe:label>
<swe:field name="gray">
<swe:Quantity definition="http://sweet.jpl.nasa.gov/2.3/propEnergyFlux.owl#SpectralRadiance">
<swe:extension>
<wcseo:rangeTypeExtension>
<wcseo:dataSemantics>http://sweet.jpl.nasa.gov/2.3/stateSpectralBand.owl#Visible</wcseo:dataSemantics>
<wcseo:dataType>http://www.opengis.net/def/dataType/OGC/0/unsignedShort</wcseo:dataType>
<wcseo:dataType2dataSemantics>
<wcseo:intervalFrom>1 4095</wcseo:intervalFrom>
<wcseo:intervalTo>390.0000 780.0000</wcseo:intervalTo>
<wcseo:type>http://sweet.jpl.nasa.gov/2.3/reprMathFunction.owl#Linear</wcseo:type>
</wcseo:dataType2dataSemantics>
</wcseo:rangeTypeExtension>
</swe:extension>
<swe:identifier>gray%20band</swe:identifier>
<swe:label>Gray Channel/Band</swe:label>
<swe:description>Gray Channel/Band</swe:description>
<swe:nilValues>
<swe:NilValues>
<swe:nilValue reason="http://www.opengis.net/def/nil/OGC/0/unknown">0</swe:nilValue>
</swe:NilValues>
</swe:nilValues>
<swe:uom code="W.m-2.sr-1.nm-1"/>
<swe:constraint>
<swe:AllowedValues>
<swe:interval>0 4095</swe:interval>
<swe:significantFigures>4</swe:significantFigures>
</swe:AllowedValues>
</swe:constraint>
</swe:Quantity>
</swe:field>
</swe:DataRecord>
</gmlcov:rangeType>
6.3.5. Range set
Cells outside the footprint hold only nil values.
Requirement 12 |
/req/eowcs/range-set-of-eo-coverage |
6.4. Dataset
A Dataset is an EO Coverage as symbolized in Figure 4. A Dataset
is either a Referenceable Dataset or a Rectified Dataset, derived from
EOWCS::ReferenceableEOCoverage
or EOWCS::RectifiedEOCoverage
, respectively.
Note
|
Typically, a Dataset represents a (single- or multi-band) satellite/aerial image scene. |
Requirement 13 |
/req/eowcs/dataset-structure |
Note
|
This definition includes the "field-of-View" of a sensor, or "cut", according to sensor specific data specification at the resolution of the sensor (also referred to as Level-0 or Level-1 data). |
6.5. Stitched Mosaic
6.5.1. Overview
A Stitched Mosaic is an identifiable, queryable, referenced EO Coverage as
symbolized in Figure 5. A Stitched Mosaic is either a
Referenceable Stitched Mosaic or a Rectified Stitched Mosaic, derived from
EOWCS::ReferenceableEOCoverage
or EOWCS::RectifiedEOCoverage
, respectively.
Stitched Mosaics refer to one or more Datasets. All cells within a Stitched
Mosaic which are not located inside any contributingFootprint
of any of the
contained Datasets carry nil values.
Requirement 14 |
/req/eowcs/referenceableStitchedMosaic-structure |
Name | Definition | Data type | Multiplicity |
---|---|---|---|
dataset |
Reference to a Referenceable Dataset referred to by the Stitched Mosaic on hand |
|
one or more (mandatory) |
Requirement 15 |
/req/eowcs/rectifiedStitchedMosaic-structure |
Name | Definition | Data type | Multiplicity |
---|---|---|---|
dataset |
Reference to a Rectified Dataset referred to by the Stitched Mosaic on hand |
|
one or more (mandatory) |
Name | Definition | Data type | Multiplicity |
---|---|---|---|
datasetId |
Dataset referred to by the Stitched Mosaic on hand |
|
one (mandatory) |
contributingFootprint |
Horizontal bounding polygon enclosing data areas of the Dataset contributing to the Stitched Mosaic on hand |
|
zero or one (optional) |
The Dataset references of an EO Coverage shall be consistent with the coverage’s EO Metadata references.
Requirement 16 |
/req/eowcs/composedOf-in-stitched-mosaic |
6.5.2. Spatio-temporal extent
A Stitched Mosaic is defined through a collection of spatially non-overlapping subsets of Datasets it refers to.
Requirement 17 |
/req/eowcs/contributingFootprint-inside-footprint |
Requirement 18 |
/req/eowcs/contributingFootprint-pairwise-disjoint |
Requirement 19 |
/req/eowcs/contributingFootprint-union-of-footprints |
Requirement 20 |
/req/eowcs/dataset-domain-set-in-stitched-mosaic-domain-set |
Datasets referred to by a Stitched Mosaic shall have aligned cell locations:
-
In case of Rectified EO Coverages, the grids of Datasets of a Stitched Mosaics shall have the same resolution.
Requirement 21
/req/eowcs/datasets-in-rectifiedStitcheMosaic-same-offsetVector
All Datasets referred to by a Rectified Stitched Mosaic shall have identical values in thegml:offsetVector
elements of their domain sets.Requirement 22
/req/eowcs/rectifiedStitchedMosaic-offsetVector
In a Rectified Stitched Mosaic instance, the value of thegml:offsetVector
elements of the domain set shall be given by the corresponding values of the Rectified Datasets the Rectified Stitched Mosaic refers to. -
In case of Referenceable EO Coverages, Datasets of Stitched Mosaics shall have aligned cell locations in overlapping areas.
Requirement 23
/req/eowcs/referenceableStitchedMosaic-domain-set
For any pair d1 and d2 of Datasets referred to by a given Stitched Mosaic, the set of point locations in the geographic overlap of the d1 and d2 domain set shall be identical.
The temporal validity of Stitched Mosaics is defined by the temporal validities of the Datasets to which the Stitched Mosaic refers.
Requirement 24 |
/req/eowcs/temporal-validity-stitched-mosaic |
6.5.3. Range type
Stitched Mosaics and their Datasets share the same range type.
Requirement 25 |
/req/eowcs/datasets-in-stitched-mosaic-same-range-type |
6.5.4. Range set
The content of a Stitched Mosaic is given by the Datasets to which it refers; cells of a Stitched Mosaic with domain coordinates outside of any embedded Dataset’s contributingFootprint carry nil values (cf. Figure 6).
Requirement 26 |
/req/eowcs/nil-values-in-stitched-mosaic |
Requirement 27 |
/req/eowcs/range-values-of-stitched-mosaic |
6.6. Dataset Series
A Dataset Series is an identifiable, queryable collection of EO Coverages and Dataset Series.
Note
|
Although named Dataset Series technically speaking it is a heterogeneous grouping of coverages and/or Dataset Series and can thus be used for any other concept like an EO Product containing multiple coverages with different resolutions as well. |
Note
|
A Dataset referred to by a Stitched Mosaic referred to by a Dataset Series is not per se referred to by that Dataset Series. However, it is allowed that such a Dataset is also referred to by the enclosing Dataset Series. |
Requirement 28 |
/req/eowcs/datasetSeries-structure |
Name | Definition | Data type | Multiplicity |
---|---|---|---|
datasetSeriesId |
Identifier of the Dataset Series on hand |
|
one (mandatory) |
footprint |
Horizontal bounding polygon enclosing valid data areas of the Dataset Series |
|
one (mandatory) |
timePeriod |
Temporal period of validity of all data in the Dataset Series |
|
one (mandatory) |
metadata |
EO Metadata of the Dataset Series on hand |
|
zero or more (optional) |
referenceableStitchedMosaic |
Referenceable Stitched Mosaic to which the Dataset Series on hand refers |
|
zero or more (optional) |
rectifiedStitchedMosaic |
Rectified Stitched Mosaic to which the Dataset Series on hand refers |
|
zero or more (optional) |
referenceableDataset |
Referenceable Dataset to which the Dataset Series on hand refers |
|
zero or more (optional) |
rectifiedDataset |
Rectified Dataset to which the Dataset Series on hand refers |
|
zero or more (optional) |
datasetSeries |
Dataset Series to which the Dataset Series on hand refers |
|
zero or more (optional) |
Note
|
A Dataset Series and a Stitched Mosaic contained therein may both refer to the same Dataset. |
The spatial extent of a Dataset Series shall enclose the spatial extents of all Stitched Mosaics, Datasets, and Dataset Series the Dataset Series refers to.
Requirement 29 |
/req/eowcs/footprint-in-datasetSeries |
Note
|
As opposed to Stitched Mosaics, Dataset Series do not require disjointness of the EO Coverages to which they refer. |
The temporal validity of a Dataset Series is defined by the union of the temporal validities of all Stitched Mosaics, Datasets, and Dataset Series to which the Dataset Series refers.
Requirement 30 |
/req/eowcs/timePeriod-in-datasetSeries |
A Dataset Series has an EO Metadata record associated.
Requirement 31 |
/req/eowcs/metadata-in-datasetSeries |
Note
|
A Dataset Series may contain multiple metadata elements holding the
metadata in different formats. Explicitly supported metadata elements are
eop:EarthObservation , gmd:MD_Metadata , gmi:MI_Metadata , mdb:MD_Metadata ,
or ows:Reference or any element in the substitutionGroup of any of these.
|
A Dataset Series shall not refer to any Dataset Series that refers to it either directly or via other Dataset Series i.e. there shall be no circular references.
Requirement 32 |
/req/eowcs/nocircularreference-of-datasetSeries |
Example: The following XML fragment shows a DatasetSeries instance.
<?xml version="1.0" encoding="UTF-8"?>
<wcseo:DatasetSeries xmlns:ows="http://www.opengis.net/ows/2.0" xmlns:gml="http://www.opengis.net/gml/3.2" xmlns:wcs="http://www.opengis.net/wcs/2.0" xmlns:wcseo="http://www.opengis.net/wcs/wcseo/1.1" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.opengis.net/wcs/wcseo/1.1 http://schemas.opengis.net/wcs/wcseo/1.1/wcsEOAll.xsd">
<wcseo:DatasetSeriesId>someDatasetSeries1</wcseo:DatasetSeriesId>
<eop:Footprint gml:id="footprint_someDatasetSeries1">
<eop:multiExtentOf>
<gml:MultiSurface gml:id="multisurface_someDatasetSeries1" srsName="EPSG:4326">
<gml:surfaceMembers>
<gml:Polygon gml:id="polygon_someDatasetSeries1">
<gml:exterior>
<gml:LinearRing>
<gml:posList>43.516667 2.1025 43.381667 2.861667 42.862778 2.65 42.996389 1.896944 43.516667 2.1025</gml:posList>
</gml:LinearRing>
</gml:exterior>
</gml:Polygon>
</gml:surfaceMembers>
</gml:MultiSurface>
</eop:multiExtentOf>
</eop:Footprint>
<gml:TimePeriod gml:id="someDatasetSeries1_timeperiod">
<gml:beginPosition>2008-03-13T00:00:00.000</gml:beginPosition>
<gml:endPosition>2008-03-13T23:59:59.999</gml:endPosition>
</gml:TimePeriod>
<ows:Metadata>
<wcseo:EOMetadata>
<ows:Reference xlink:href="http://www.someCatalogue.org/eop-metadata-from-someDatasetSeries1" xlink:role="http://standards.iso.org/iso/19115/-3/mdb/1.0" xlink:title="ISO 19115-3 Metadata" />
</wcseo:EOMetadata>
</ows:Metadata>
<wcseo:rectifiedDataset>
<wcs:CoverageId>someEOCoverage1</wcs:CoverageId>
</wcseo:rectifiedDataset>
</wcseo:DatasetSeries>
7. EO service model
7.1. Overview
This Clause defines request types and their responses for operations on EO Coverages. EO Coverages can be offered by a WCS server alongside with any other type of coverage. Behavior of the service on non-EO Coverages remains unchanged.
7.2. GetCapabilities operation
7.2.1. GetCapabilities request
The GetCapabilities request is extended over WCS Core [OGC 09-110r4] as follows:
-
In the
sections
request parameter, values "DatasetSeriesSummary" and "CoverageSummary" are allowed in addition to those defined in OWS Common [06-121r9].
Requirement 33 |
/req/eowcs/getCapabilities-request-sections |
7.2.2. GetCapabilities response
The GetCapabilities response is extended over WCS Core [OGC 09-110r4] as follows:
-
There is an additional
DatasetSeriesSummary
section reporting identifiers of Dataset Series offered by the service on hand; -
There is an optional constraint
CountDefault
specifying the maximum number ofCoverageDescription
andDatasetSeriesDescription
elements reported in aDescribeEOCoverageSet
response; and -
For the eowcs_geteocoverageset conformance class there is an additional
<wcseo:wcseoMetadata
element inside thewcs:Extension
element of thewcs:ServiceMetadata
element to specify default and supported package formats for the GetEOCoverageSet operation.
Note
|
An EO-WCS server may choose to not report, in the CoverageSummary
section of a GetCapabilities response, the identifiers of Stitched Mosaic
coverages referred to by some Dataset Series and the identifiers of Dataset
coverages referred to by some Stitched Mosaic or Dataset Series.
|
In a GetCapabilities response, a server announces availability of this EO-WCS like an extension.
Requirement 34 |
/req/eowcs/getCapabilities-response-conformance-class-in-profile |
Requirement 35 |
/req/eowcs_geteocoverageset/getCapabilities-response-conformance-class-in-profile |
Requirement 36 |
/req/eowcs/getCapabilities-response-structure |