Difference between revisions of "IOOS Gateway"

From OPeNDAP Documentation
(WCS Server (to provide WCS access to data served via DAP2))
 
Line 1: Line 1:
Changes to the DAP, Hyrax, or other proposals stemming from the IOOS Gateway Project.  
+
Changes to the DAP, Hyrax, or other proposals stemming from the WCS Gateway Project.  
  
  
Much of the IOOS gateway work is focused on:
+
Much of the WCS gateway work is focused on:
  
 
# Providing DAP2 protocol access to WCS served data.
 
# 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 access to data served by WCS ===
Line 16: Line 15:
  
 
----
 
----
=== 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.
 
 
* [[WCS GetCapabilities]]
 
* [[WCS Describe Coverage]]
 
* [[WCS GetCoverage]]
 
** [[WCS  Coverage Processing]]
 

Latest revision as of 17:30, 29 April 2009

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


Much of the WCS gateway work is focused on:

  1. Providing DAP2 protocol access to WCS served data.

1 DAP2 access to data served by WCS

1.1 DAP2.1 Namespace

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