Copyright © 2010 Open Geospatial Consortium
57
15 JoinData operation optional
15.1 Introduction
The JoinData operation instructs the server to merge an attribute data table encoded in GDAS format i.e. obtainable via a GetData request with its spatial framework. The
server performs the join and prepares the output in the form requested by the client. The response includes the connection information required to access the outputs.
This operation shall be supported for all servers that implement data joining, as identified in section 6.1.2.
15.2 JoinData operation request
15.2.1 JoinData request parameters
A request to perform the JoinData operation shall include the parameters listed in Table 71. 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.
58
Copyright © 2010 Open Geospatial Consortium
Table 71 — Parameters in JoinData 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 “JoinData” 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
update Identifies if JoinData products
should by updatedupdatable. Boolean type
Value is “true” or “false”. Default is “false”.
Zero or one optional
a
Framework URI
The URI of the spatial framework.
URI type Value is a FrameworkURI
found in the DescribeJoinAbilities
response. One mandatory
GetDataURL A URL which returns the
attribute data table encoded in GDAS format.
URI type Value is a URL that returns a
valid GDAS document compliant with this version
of this standard.
b
One mandatory
StylingURL URL that contains the styling
information to be applied to any WMS output.
URI type Value is a URL that returns
valid styling information. Zero or one
optional
c
Styling Identifier
Name that identifies the type of styling to be invoked.
Character String type, not empty
Value is an Identifier listed in the DescribeJoinAbilities
response. Zero or one
optional
d
Classification URL
URL that returns a file describing a data classification
to be applied to the output e.g. the classification to be used for
a legend in the case where the output is a WMS.
e
URI type Value is a URL that returns
valid classification information.
Zero or one optional
f
Copyright © 2010 Open Geospatial Consortium
59
a Include when the user will wish to update the products of this request in the future and requires that the URLs of the output products shall not change. If this parameter is true then the service shall attempt to update an existing set of JoinData
products produced earlier by an earlier identical request. If no such products exist it shall prepare JoinData products for this request in such a way that they can be updated by subsequent identical JoinData requests. URLs for such products shall not
vary for subsequent update requests. b Note that this may be a TJS GetData request via HTTP GET, a stored response to a GetData request, or a web process
that returns content compliant with the GetData response schema. If more than one attribute of type “Data” exists in the response to this URL, the server shall apply the JoinData operation to the first attribute of type “Data”.
c If this parameter is absent, the server will apply its default styling to any WMS output. d If this parameter is absent, the server will assume that the StylingURL, if present, is the default form of styling supported
by the server. e This file must be encoded in compliance with the XML Schema identified in the ClassificationSchemaURL element of the
DescribeJoinAbilities response. f If this parameter is absent, the server will apply a default classification as determined by the server.
NOTE 1 The parameters shaded in gray above are largely copied from Table 3 of this document.
15.2.2 JoinData request KVP encoding mandatory
Kategori