You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
10.3.1 Introduction
The normal response to a valid GetCoverage operation request shall be a single coverage extracted from the coverage requested, with the specified spatial reference system, bounding box, size, format, and range subset.
But we could also support:
10.3.11 Response encodings
10.3.11.1 Overview
The encoding of the GetCoverage response consists of a Coverages XML document (see 10.3.11.2 below), packaged and bundled according to the request encoding and the value of the ―store‖ parameter (see Table 24). WCS servers shall implement response encodings according to Table 31.
This additional feature would allow us to support much more complete TimeSequence queries for arbitrary lists of TimePeriods or TimeIntervals.
It's likely that this implementation would also require implementing the store parameter to fully support the spec.
To verify that these types of requests are not currently supported by gt server, I made a request to:
The WCS 1.1.1 spec supports returning a GetCoverage response as an XML document according to https://portal.opengeospatial.org/files/07-067r2
We currently implement:
But we could also support:
This additional feature would allow us to support much more complete TimeSequence queries for arbitrary lists of TimePeriods or TimeIntervals.
It's likely that this implementation would also require implementing the
store
parameter to fully support the spec.To verify that these types of requests are not currently supported by gt server, I made a request to:
http://localhost:9000/?SERVICE=WCS&VERSION=1.1.1&REQUEST=GetCoverage&FORMAT=xml&IDENTIFIER=us-ned&<...>
And got:
Error parsing parameters: Unsupported format: 'xml'
.Example
Taken from the same WCS 1.1.1 spec:
The text was updated successfully, but these errors were encountered: