36
Copyright © 2010 Open Geospatial Consortium
06-121r3]. The allowed standard exception codes shall include those listed in Table 20 of that document. For each listed exceptionCode, the contents of the “locator” parameter
value shall be as specified in the right column of Table 44.
Table 44 — Exception codes for DescribeFrameworks operation
exceptionCode value Meaning of code
“locator” value
OperationNotSupported Request is for an operation that is not supported by this server
Name of operation not supported
MissingParameterValue Operation request does not include a parameter value, and this server did not declare a default
value for that parameter Name of missing
parameter InvalidParameterValue
Operation request contains an invalid parameter value
Name of parameter with invalid value
OptionNotSupported Request is for an option that is not supported
by this server Identifier of option
not supported
NoApplicableCode No other exceptionCode specified by this service
and server applies to this exception None, omit “locator”
parameter NOTE The values listed above are copied from Table 20 in Subclause 8.3 of [OGC 06-121r3].
10 DescribeDatasets operation optional
10.1 Introduction
The DescribeDatasets operation returns an XML document that identifies all of the matching attribute datasets for which data is available from the service instance. There
may be one or more attribute datasets that apply to any spatial framework. The response includes descriptive information about each dataset available from the service instance,
and information that uniquely identifies each dataset. This description can be used to automatically build a user interface to identify the dataset from which the user would like
to obtain attribute data. When the optional DatasetURI parameter is included, the response can be used to populate an “about” page for a specific dataset.
This operation shall be supported for all servers that implement data access, as identified in section 6.1.1.
10.2 DescribeDatasets operation request
10.2.1 DescribeDatasets request parameters
A request to perform the DescribeDatasets operation shall include the parameters listed in Table 45. This table also specifies the source of values and multiplicity of each listed
parameter, plus the meaning to servers when each optional parameter is not included in the operation request.
Copyright © 2010 Open Geospatial Consortium
37
Table 45 — Parameters in DescribeDatasets operation request
Names Definition
Data type and values Multiplicity and use
service Service type identifier
Character String type, not empty Value is “TJS”
One mandatory request
Operation name Character String type, not empty
Value is “DescribeDatasets” One mandatory
version Service version
identifier Character String type, not empty
Value is “1.0” Zero or one
optional When included,
return the matching version
When omitted, return latest supported
version language
Language identifier for human readable text
Character String type, not empty Value is a two or five character
IETF RFC 4646 language identifier
Zero or one optional
For use see section 7.6
Framework URI
URI of a spatial framework to which
the attribute data can be joined.
URI type, not empty Value is a URI as found in the
DescribeFrameworks response. Zero or one
optional
a
DatasetURI URI of an attribute table,
which can be joined to the spatial framework
identified by the FrameworkURI.
URI type, not empty Value is a DatasetURI as found in
the DescribeDatasets response. Zero or one
optional
b
a If this parameter is absent, the response shall include descriptions for all frameworks for which data access is supported by the server.
b DatasetURIs are normally unknown during an initial DescribeDatasets request to the server, and therefore this parameter is normally absent from such a request. If this parameter is absent, the response shall include descriptions for all datasets
available for the specified frameworks.
NOTE 1 The parameters shaded in gray above are largely copied from Table 3 in Subclause 7.3 of this document. NOTE 2: The values for all fields shall be encoded using the standard Internet practice for encoding URLs [IETF
RFC 1738].
10.2.2 DescribeDatasets request KVP encoding
