SPS Application Profile for EO Sensors OGC 07-018r2
Copyright © 2008 Open Geospatial Consortium, Inc. All Rights Reserved.
37
10. GetCapabilities operation mandatory, synchronous
10.1. Introduction
The mandatory GetCapabilities operation allows clients to retrieve service metadata from a server. The response to a GetCapabilities request shall be an XML document containing service metadata
about the server, including specific information about a SPS. This clause specifies the XML document that a SPS server must return to describe its capabilities.
10.2. EO profile specific
- The description of the sensors has been removed from the capabilities. Reason: the
description is returned by the DescribeSensor operation. -
The content section of the capabilities contains the supported communication protocols. For SPS EO profile, the communication protocol is SOAP with WS-Addressing.
-
PhenomenonOfferingList
element has been removed.
10.3. Capabilities schema
The following diagram shows the content of the response sent by the SPS to a GetCapabilities request:
Figure 9-5 - Capabilities schema
10.4. GetCapabilities Operation request
The GetCapabilities operation request shall be as specified in Subclauses 7.2 and 7.3 of [OGC 05- 008]
. The value of the “service” parameter shall be “SPS”. The allowed set of service metadata or Capabilities XML document section names and meanings shall be as specified in Tables 3 and 7
of [OGC 05-008]. The “Multiplicity and use” column in Table 1 of [OGC 05-008] specifies the optionality of each
listed parameter in the GetCapabilities operation request. The following table specifies the implementation of those parameters by Programming Service clients and servers.
SPS Application Profile for EO Sensors OGC 07-018r2
Copyright © 2008 Open Geospatial Consortium, Inc. All Rights Reserved.
38
Name Multiplicity
Client implementation Server implementation
service One
mandatory Each
parameter shall
be implemented by all clients,
using specified value Each parameter shall be implemented
by all servers, checking that each parameter is received with specified
value request
One mandatory
Accept Versions
Zero or one optional
Should be implemented by all software
clients, using
specified values Shall be implemented by all servers,
checking if parameter is received with specified values
Sections Zero or one
optional Each
parameter may
be implemented by each client
If parameter not provided, shall expect default response
If parameter provided, shall allow default or specified
response Each parameter may be implemented
by each server If parameter not implemented or not
received, shall
provide default
response If
parameter implemented
and received, shall provide specified
response update
Sequence Zero or one
optional Accept
Formats Zero or one
optional
Table 9-2: Implementation of parameters in GetCapabilities operation request
All SPS servers shall implement HTTP GET transfer of the GetCapabilities operation request, using KVP encoding. Servers may also implement HTTP POST transfer of the GetCapabilities
operation request, using XML encoding only.
10.5. GetCapabilities Operation response
