WCS 1.0.0 Change Request - Add SupportedFormat and SupportedCRS to Contents
Open Geospatial Consortium
OGC Doc 06-110
CR-Form-v3
CHANGE REQUEST
WCS 1.0.0 CR ?
rev
-
Current version:
1.0.0
For HELP on using this form, see bottom of this page or look at the pop-up text over the symbols.
Proposed change affects:
AS
Imp Spec X
Recom. Paper
Title:
Add SupportedFormat and SupportCRS to Contents
Source:
PCI Geomatics & WCS revision working group
Work item code:
Category:
Other
Date: July 17, 2006
B
Use one of the following categories:
F (Critical correction)
A (corresponds to a correction in an earlier
release)
B (Addition of feature),
C (Functional modification of feature)
D (Editorial modification)
Detailed explanations of the above categories can
be found in the TC Policies and Procedures.
Reason for change:
1) Adds a way for a WCS client to determine if it can interoperate with a WCS
vis-à-vis the supported formats and CRSs without having read the entire
capabilities document.
2) To describe a dependency of supportedCRS on supportedFormats.
Summary of change: 1) Add the SupportedFormat and SupportedCRS (with multiplicity 0 or more)
parameters to the Contents object. These parameters are the union of all of
the supportedFormats and supported CRS from the coverage descriptions,
briefs (summies).
2) Add a clause describing that the possible dependency between supportedCRS
and supportedFormat is not considered by this server.
Consequences if
not approved:
Clients will have to do extra work to determine if they can interoperate with a
particular WCS. This reduces the workload on the client. Note that clients still
have to do the work if the server implementation does not add these parameters.
Clauses affected:
8.3.3.1 Overview
10.3.3.1 SupportFormat and SupportedCRS dependencies
Other specs
X Other core specifications
Affected:
Other comments:
This feature could be added to OWS
Common as well. However, since this is the
first time such an idea has been introduced
into OGC specifications, it should be
evaluated first.
Abstract specifications
Recommendation Papers
This feature was discussed by the WCS RWG and added to document 06-083r2
The OGC Technical Committee Policies & Procedures 05-020r3
before this actual change request was written. This change request is to make it
official.
Add or modify the following Sections:
8.3.3.1 Overview
Table 1 — Parts of Contents section
Name
Definition
Data type
Multiplicity and
use
coverageSu
mmary
CoverageS
ummary
Brief metadata
describing a top-level
coverage available
from this WCS server
CoverageSummary
data
structure,
see Error:
Reference
source not
found
Zero or more
(optional) a
One for each
coverage
available, unless
OtherSource is
used
supportedC
RS
Supported
CRS
CRS in which
GetCoverage
operation response
may be expressed.
URI
Zero or more
(optional)
Include one for
each CRS
supported b,c,e
supportedF
ormat
SupportedF
ormat
Format in which
GetCoverage
operation response
may be encoded
CharacterS
tring type
Zero or more
(optional)
Include one for
each format
supported b,d,e
otherSourc
e
OtherSourc
e
Reference to another
source of contents
metadata
CI_Online
Resource
class in
ISO 19115
Zero or more
(optional)
Include when
useful
a
Shall be included unless the OtherSource is included and all this metadata is available from that source.
b
There may be a dependency of SupportedCRS on SupportedFormat, as described in clause .
c
This list of SupportedCRSs shall be the union of all of the supported CRSs in all of the nested CoverageSummaries,
d This list of SupportedFormats shall be the union of all of the supported formats in all of the nested
CoverageSummaries.
e Servers should implement this feature as it reduces the effort clients require to determine that they can interoperate with
the server.
10.3.3.1 SupportFormat and SupportedCRS dependencies
Some formats require that the data be stored in a specific CRS, or the CRS must be chosen from a
small list of CRSes. The dependency between CRSes and formats can not be expressed in this
specification. When a WCS server receives a request where the requested output format and the
requested output CRS are incompatible then the server shall return an UnsupportedCombination
exception, see Error: Reference source not found.
Last Revision Date: 2 December 2017
Page2
OGC Doc 06-110
CR-Form-v3
CHANGE REQUEST
WCS 1.0.0 CR ?
rev
-
Current version:
1.0.0
For HELP on using this form, see bottom of this page or look at the pop-up text over the symbols.
Proposed change affects:
AS
Imp Spec X
Recom. Paper
Title:
Add SupportedFormat and SupportCRS to Contents
Source:
PCI Geomatics & WCS revision working group
Work item code:
Category:
Other
Date: July 17, 2006
B
Use one of the following categories:
F (Critical correction)
A (corresponds to a correction in an earlier
release)
B (Addition of feature),
C (Functional modification of feature)
D (Editorial modification)
Detailed explanations of the above categories can
be found in the TC Policies and Procedures.
Reason for change:
1) Adds a way for a WCS client to determine if it can interoperate with a WCS
vis-à-vis the supported formats and CRSs without having read the entire
capabilities document.
2) To describe a dependency of supportedCRS on supportedFormats.
Summary of change: 1) Add the SupportedFormat and SupportedCRS (with multiplicity 0 or more)
parameters to the Contents object. These parameters are the union of all of
the supportedFormats and supported CRS from the coverage descriptions,
briefs (summies).
2) Add a clause describing that the possible dependency between supportedCRS
and supportedFormat is not considered by this server.
Consequences if
not approved:
Clients will have to do extra work to determine if they can interoperate with a
particular WCS. This reduces the workload on the client. Note that clients still
have to do the work if the server implementation does not add these parameters.
Clauses affected:
8.3.3.1 Overview
10.3.3.1 SupportFormat and SupportedCRS dependencies
Other specs
X Other core specifications
Affected:
Other comments:
This feature could be added to OWS
Common as well. However, since this is the
first time such an idea has been introduced
into OGC specifications, it should be
evaluated first.
Abstract specifications
Recommendation Papers
This feature was discussed by the WCS RWG and added to document 06-083r2
The OGC Technical Committee Policies & Procedures 05-020r3
before this actual change request was written. This change request is to make it
official.
Add or modify the following Sections:
8.3.3.1 Overview
Table 1 — Parts of Contents section
Name
Definition
Data type
Multiplicity and
use
coverageSu
mmary
CoverageS
ummary
Brief metadata
describing a top-level
coverage available
from this WCS server
CoverageSummary
data
structure,
see Error:
Reference
source not
found
Zero or more
(optional) a
One for each
coverage
available, unless
OtherSource is
used
supportedC
RS
Supported
CRS
CRS in which
GetCoverage
operation response
may be expressed.
URI
Zero or more
(optional)
Include one for
each CRS
supported b,c,e
supportedF
ormat
SupportedF
ormat
Format in which
GetCoverage
operation response
may be encoded
CharacterS
tring type
Zero or more
(optional)
Include one for
each format
supported b,d,e
otherSourc
e
OtherSourc
e
Reference to another
source of contents
metadata
CI_Online
Resource
class in
ISO 19115
Zero or more
(optional)
Include when
useful
a
Shall be included unless the OtherSource is included and all this metadata is available from that source.
b
There may be a dependency of SupportedCRS on SupportedFormat, as described in clause .
c
This list of SupportedCRSs shall be the union of all of the supported CRSs in all of the nested CoverageSummaries,
d This list of SupportedFormats shall be the union of all of the supported formats in all of the nested
CoverageSummaries.
e Servers should implement this feature as it reduces the effort clients require to determine that they can interoperate with
the server.
10.3.3.1 SupportFormat and SupportedCRS dependencies
Some formats require that the data be stored in a specific CRS, or the CRS must be chosen from a
small list of CRSes. The dependency between CRSes and formats can not be expressed in this
specification. When a WCS server receives a request where the requested output format and the
requested output CRS are incompatible then the server shall return an UnsupportedCombination
exception, see Error: Reference source not found.
Last Revision Date: 2 December 2017
Page2