IOOS Gateway: Difference between revisions
From OPeNDAP Documentation
⧼opendap2-jumptonavigation⧽
(→WCS) |
|||
| Line 18: | Line 18: | ||
=== WCS Server (to provide WCS access to data served via DAP2) === | === WCS Server (to provide WCS access to data served via DAP2) === | ||
A WCS server must support three basic operations, GetCapabilities, DescribeCoverage, and GetCoverage. All of the currently existing specifications for WCS (1.0.x, 1.0+, 1.1.x, | A WCS server must support three basic operations, GetCapabilities, DescribeCoverage, and GetCoverage. All of the currently existing specifications for WCS (1.0.x, 1.0+, 1.1.x, ''more?'' ) define a KVP encoded request (a URL to be used in an HTTP GET transaction) API and a SOAP API. Both API's provide the same three interfaces. | ||
* [[WCS GetCapabilities]] | * [[WCS GetCapabilities]] | ||
Revision as of 22:50, 11 July 2008
Changes to the DAP, Hyrax, or other proposals stemming from the IOOS Gateway Project.
Much of the IOOS gateway work is focused on:
- Providing DAP2 protocol access to WCS served data.
- Providing WCS access to data served by OPeNDAP servers.
DAP2 access to data served by WCS
DAP2.1 Namespace
There have been some proposed changes to the DAP2 namespace (for the DDX) to hep accommodate this work.
WCS Server (to provide WCS access to data served via DAP2)
A WCS server must support three basic operations, GetCapabilities, DescribeCoverage, and GetCoverage. All of the currently existing specifications for WCS (1.0.x, 1.0+, 1.1.x, more? ) define a KVP encoded request (a URL to be used in an HTTP GET transaction) API and a SOAP API. Both API's provide the same three interfaces.
