DAP4: Data Service: Difference between revisions
From OPeNDAP Documentation
⧼opendap2-jumptonavigation⧽
(Created page with "== Overview == The Data Service is invoked by appending the suffix .dap to the file part of the dataset's referent (aka base) URL. The Data response is a multipart MIME document...") |
No edit summary |
||
| Line 1: | Line 1: | ||
== Overview == | == Overview == | ||
The Data Service | The Data Service provides DAP4 data access to a dataset. | ||
== Request == | == Request == | ||
The Data Service is invoked by appending the suffix <font size="2"><code>.dap</code></font> to the file part of the dataset's referent (aka base) URL and then dereferencing the new URL. The Data service accepts a query string (constraint expression). | |||
[[DAP4:_Requests#Data_Request | DAP4: Data Request]] | [[DAP4:_Requests#Data_Request | DAP4: Data Request]] | ||
== Response == | == Response == | ||
The Data response is a multipart MIME document that contains a N+1 parts for a response with N variables. | |||
[[DAP4:_Responses#Data_Response | DAP4: Data Response]] | [[DAP4:_Responses#Data_Response | DAP4: Data Response]] | ||
== Errors == | == Errors == | ||
Latest revision as of 20:54, 29 March 2012
Overview
The Data Service provides DAP4 data access to a dataset.
Request
The Data Service is invoked by appending the suffix .dap to the file part of the dataset's referent (aka base) URL and then dereferencing the new URL. The Data service accepts a query string (constraint expression).
Response
The Data response is a multipart MIME document that contains a N+1 parts for a response with N variables.
