WPS GetCapabilities Operation
The GetCapabilities operation provides access to general information about a live WPS implementation, and lists the operations and access methods supported by that implementation. WPS implementations must support the GetCapabilities operation via HTTP GET. Support for HTTP POST is optional.
|Request||Required||Identifies service request. Must be "GetCapabilities".|
|Service||Required||Identifies service type. Must be "WPS".|
|AcceptVersions||Optional||Identifies service version. Comma-delimited string of version numbers supported by the client, in order of preference. Currently "1.0.0" is the only valid version number.|
|Language||Optional||Determines the language of the human-readable content of the response. Contains a valid two or five digit RFC 4646 language tag.|
HTTP GET method using KVP (mandatory)
HTTP GET requests supply the request parameters encoded as KVP pairs as part of the URL. An example of a GetCapabilities request via HTTP GET is:
HTTP POST method using XML (optional)
XML encoded GetCapabilities requests use the HTTP POST method with the body of the request (POST data) of type text/xml according to the GetCapabilities request XML schema. For example, a client may encode a GetCapabilities request in XML as follows:
<GetCapabilities service="WPS" acceptVersions="1.0.0" language="en-CA">
SOAP-encoded GetCapabilities requests and responses use SOAP document-style encoding (also called message-style or document-literal encoding), as described in [OWS 06-094]. WPS SOAP messages simply contain a normal XML-encoded request or response wrapped in a SOAP envelope.
The normal response to a GetCapabilities request is a WPS Capabilities document. This document is encoded in XML according to the GetCapabilities response XML schema.
- View schema documentation
- Download complete OGC schema package (note, WPS will require modification of an OWS Common file, as indicated in Annex B of the WPS specification).
When a WPS server encounters an error while performing a GetCapabilities operation, it shall return an exception report message as specified in Clause 8 of [OGC 06-121r3]. The allowed exception codes shall include those listed in Table 5 of Subclause 7.4.1 of [OGC 06-121r3].
For more information on structuring requests, please see the WPS Standard.