Difference between revisions of "IOOS Gateway"

From OPeNDAP Documentation
(WCS Server (to provide WCS access to data served via DAP2))
(WCS Server (to provide WCS access to data served via DAP2))
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.  
+
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, ad there is probably a 1.2.x I am not yet privy to) define a KVP encoded (a URL to be used in an HTTP GET transaction) request API and a SOAP API. Both API's provide the same three interfaces.
 +
 
 
* [[WCS GetCapabilities]]
 
* [[WCS GetCapabilities]]
 
* [[WCS Describe Coverage]]
 
* [[WCS Describe Coverage]]
 
* [[WCS GetCoverage]]
 
* [[WCS GetCoverage]]
 
** [[WCS  Coverage Processing]]
 
** [[WCS  Coverage Processing]]

Revision as of 18:44, 11 July 2008

Changes to the DAP, Hyrax, or other proposals stemming from the IOOS Gateway Project.


1 WCS

Much of the IOOS gateway work is focused on:

1. Providing DAP2 protocol access to WCS served data. 1. Providing WCS access to data served by OPeNDAP servers.

1.1 DAP2 access to data served by WCS

1.1.1 DAP2.1 Namespace

There have been some proposed changes to the DAP2 namespace (for the DDX) to hep accommodate this work.

1.2 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, ad there is probably a 1.2.x I am not yet privy to) define a KVP encoded (a URL to be used in an HTTP GET transaction) request API and a SOAP API. Both API's provide the same three interfaces.