Data Domain Statistics (DDS)

DDS User Interface is the application that responds to the users data requests and displays the results of the requested statistical analysis. This is a custom piece of software that will need to be designed and developed.

This interface:

will accept XML requests containing a layer identifier and FID list.
will accept an XML request that includes the layer ID, FID list, the named attributes to query on, statistical analysis type (num or alpha) and return type (report in html, XML or plain text). This will allow the DDS to respond with a reply without invoking its user interface.
presents the user with a list of layer attributes their data types and the number of records for the requested layer.
presents upon request the raw data returned for the requested layer attributes and FIDs.
allows multiple selection of attributes to run statistical analysis on.
allows user to override the default analysis type (numeric or alpha).
allows user to weight the analysis using one of the attribute columns.
allows user to save the requested raw data or the results of the statistical analysis as XML.
allows user to save the returned presentation of statistical analysis as a file (click 'Save As' in browser).
reports all errors in the DDS process.

Further Clarification

The service components can be implemented as either C/CGI or Java/Servlets (Tomcat).
Exception handling: A strong emphasis should be put on proper exception handling in the XML specifications.
Multi-language: The exception messages produced by each component should be available in English and French.

Main DDS Specification

Introduction

The Main DDS server is responsible for collecting data from a DAS or GDAS server, pushing it through analysis on a Stats Analyzer server, and then formatting the data for presentation through a Stats Presenter service. It doesn't do much actual work itself. The service request to the DDS consists primarily of requests that are passed on directly to other servers, already formatted in the form(s) appropriate to those servers.

The DDS server implements a GetCapabilities request and a DDSRequest service.

Exceptions

In the event that a Web service encounters an error while processing a request or receives an unrecognized request, it shall generate an XML document indicating that an error has occurred. The format of the XML error response is specified by, and must validate against, the exception response schema.

A ServiceExceptionReport element can contain one or more processing exceptions. The mandatory version attribute is used to indicate the version of the service exception report schema. For this version of the specification, this value is fixed at 1.2.0.

Individual exception messages are contained within the ServiceException element. The optional code attribute may be used to associate an exception code with the accompanying message. The optional locator attribute may be used to indicate where an exception was encountered in the request that generated the error.

A number of elements defined in this document include a handle attribute that can be used to associate a mnemonic name with the element. If such a handle exists, its value may be reported using the locator attribute of the ServiceException element. If the handle attribute is not specified, then a server implementation may attempt to locate the error using other means, such as line numbers, etc.

The returned exception should always have the mime type text/xml.

Example

The following is an example of an exception report. This exception indicates that the first insert statement failed because of a missing closing XML tag in the request.

<?xml version="1.0" ?>
<ServiceExceptionReport
     version="1.2.0"
     xmlns="http://www.opengis.net/ogc"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="http://www.opengis.net/ogc ../wfs/1.0.0/OGC-exception.xsd">
  <ServiceException">
     statistical operation CONVEX_HULL not supported by this server
  </ServiceException>
</ServiceExceptionReport>

It should be noted that this sample output validates against the exception report schema presented above.

GetCapabilities Operation

Each DDS Server must describe its capabilities. This clause defines an XML document structure intended to convey general information about the service itself, and summary information about the available operations supported by this server.

GetCapabilities Request

Key-value Pair Encoding

The following keywords are defined for KeyValuePair requests:

Table 1. KeyValuePair Requests - DDS

Request Parameter	Required/Optional	Description
`REQUEST=GetCapabilities`	Required	Request Name
`VERSION=0.1.0`	Optional	Request Version
`SERVICE=DDS`	Required	Service Type
`ORIGINSERVERURI=<originserver_uri>`	Optional	Data Restriction Criteria
`ORIGINSERVERFIELD=<originserver_field>`	Optional	Data Restriction Criteria

The VERSION and SERVICE parameters, respectively, denote the version number of the specification and the service it addresses. For DDS requests, the SERVICE parameter must have the value "DDS".

The optional ORIGINSERVERURI and ORIGINSERVERFIELD indicate the identity of the service and the fieldname that will be used as the input feature ids when the data is later requested. It is used by the GetCapabilities to restrict the set of datasources returned to those that are applicable to the service and field in question.

NOTE: When making requests of a WSP server, which may offer other OGC Web Services as well, the SERVICE parameter indicates that the client seeks information about the DDS server in particular.

For simplicity, the SECTION and UPDATESEQUENCE keywords found in some OGC Web Services has been omitted from this specification but may be supported in future versions.

XML Encoding

XML encoded GetCapabilities requests take the following form:

Table 2. XML Encoded GetCapabilities Requests- DDS

Attribute	Required/Optional	Description
`version`	Optional	Request version. Defaults to the latest available version, currently 0.1.0
`service`	Required	Service Type, must be DDS
`OriginServerURI`	Optional	Data Restriction Criteria
`OriginServerField`	Optional	Data Restriction Criteria

For example, a client may encode a GetCapabilities request in XML as follows:

<GetCapabilities version="0.1.0" service="DDS"
  OriginServerURI="http://maptools.org/cgi-bin/wms"
  OriginServerField="FID" />

GetCapabilities Response

The GetCapabilities request returns an XML document describing the capabilities of the server. This document includes the generic Service and Capability sections common to all OGC Web Services. These sections are not described in detail here.

Description

Also under the Capabilities tag, the DDS service will have StatisticalOperations, StatisticalPresentations, and GeolinkedData elements. The StatisticalOperations and StatisticalPresentations tags take exactly the same form as they would in the capabilities of the WSA and WSP services, and they would normally be copied into the DDS capabilities from the capabilities of the default WSA and WSP services for the DDS service.

The GeolinkedData element contains descriptions of all DataSets (nested within their Framework information) that are applicable for the OriginServerURI and OriginServerField specified in the GetCapabilities call that are known to the DDS server. If no OriginServerURI or OriginServerField are provided, then all known datasets are included in the capabilities. Furthermore, the Framework elements will have an extra href attribute containing a reference to the GDAS server from which they are derived.

A fragment showing the start of a dataset might look like this:

    <GeolinkedData>
      <Framework href="http://www2.dmsolutions.ca/msapps/gdas/gdas.php">
        <organization>Environment Canada</organization>
        <domain>ec.gc.ca</domain>
        <name>Ecoregion(shape)</name>
        <title>Ecoregions of Canada</title>
        <description>Ecoregions of Canada, forming part of the
          Terrestrial Ecological Stratification of Canada.</description>

        <version>1</version>
        <releasedate>1995-06-03</releasedate>
        <documentation>http://sis.agr.gc.ca/cansis/nsdb/ecostrat/region/</documentation>
        <geolinkagefield>ecoregion</geolinkagefield>
        <DataSet>
          <organization>Agriculture and Agri-Food Canada</organization>

          <domain>agr.gc.ca</domain>
          <name>1961-90ClimateNormals</name>
...

Full Capabilities Example

<?xml version="1.0" encoding="iso-8859-1"?>
<DDS_Capabilities xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="0.1.0">
  <Service>
    <Name>DDS</Name>
    <Title>Main Data Domain Statistics Server</Title>
    <Abstract>Service Providing Data Retreival, Statistcal Analysis and Presentation Operations</Abstract>
    <KeywordList>
      <Keyword>Statistics</Keyword>

      <Keyword>Analysis</Keyword>
    </KeywordList>
    <OnlineResource xmlns:xlink="http://www.w3c.org/1999/xlink"
      xlink:type="simple" xlink:href="http://www.dmsolutions.ca"/>
    <ContactInformation>
      <ContactPersonPrimary>
        <ContactPerson>Frank Warmerdam</ContactPerson>
        <ContactOrganization>DM Solutions Group</ContactOrganization>

      </ContactPersonPrimary>
      <ContactPosition>Software Developer</ContactPosition>
      <ContactAddress>
        <AddressType>postal</AddressType>
        <Address>15 - 85 Baif Blvd.</Address>
        <City>Richmond Hill</City>
        <StateOrProvince>Ontario</StateOrProvince>

        <PostCode>L4C 5E2</PostCode>
        <Country>Canada</Country>
      </ContactAddress>
      <ContactVoiceTelephone>++011 905 7800450</ContactVoiceTelephone>
      <ContactFacsimileTelephone>++011 905 7800450</ContactFacsimileTelephone>
      <ContactElectronicMailAddress>warmerdam@pobox.com</ContactElectronicMailAddress>

    </ContactInformation>
    <Fees>none</Fees>
    <AccessConstraints>none</AccessConstraints>
  </Service>
  <Capability>
    <Request>
      <GetCapabilities>
        <Format>String</Format>

        <DCPType>
          <HTTP>
            <Get>
              <OnlineResource xmlns:xlink="http://www.w3c.org/1999/xlink"
                xlink:type="simple" xlink:href="http://maptools.org/cgi-bin/wsa?"/>
            </Get>
            <Post>
              <OnlineResource xmlns:xlink="http://www.w3c.org/1999/xlink"
                xlink:type="simple"
                xlink:href="http://maptools.org/cgi-bin/wsa?"/>
            </Post>
          </HTTP>

        </DCPType>
      </GetCapabilities>
      <DDSRequest>
        <Format>String</Format>
        <DCPType>
          <HTTP>
            <Post>
              <OnlineResource xmlns:xlink="http://www.w3c.org/1999/xlink"
                xlink:type="simple"
                xlink:href="http://maptools.org/cgi-bin/wsa?"/>

            </Post>
          </HTTP>
        </DCPType>
      </DDSRequest>
    </Request>
    <StatisticalOperations>
      <StatsOp>
        <Name>mean</Name>

        <Description>Computes the euclidean mean of the given numeric values -
          by summing and dividing by the value count</Description>
        <DataInput>
          <attribute>
            <Name>Input</Name>
          </attribute>
        </DataInput>
        <DataResult>
          <attribute>

            <Name>Mean</Name>
          </attribute>
        </DataResult>
      </StatsOp>
      <StatsOp>
        <Name>min</Name>
        <Description>Returns the minimum value of the input numeric values</Description>

        <DataInput>
          <attribute>
            <Name>Input</Name>
          </attribute>
        </DataInput>
        <DataResult>
          <attribute>
            <Name>Minimum</Name>

          </attribute>
        </DataResult>
      </StatsOp>
      <StatsOp>
        <Name>max</Name>
        <Description>Returns the maximum value of the input numeric values</Description>
        <DataInput>
          <attribute>

            <Name>Input</Name>
          </attribute>
        </DataInput>
        <DataResult>
          <attribute>
            <Name>Maximum</Name>
          </attribute>
        </DataResult>

      </StatsOp>
      <StatsOp>
        <Name>mode</Name>
        <Description>Returns the mode value of the input numeric values.
          The mode is the most frequently occurring input value.</Description>
        <DataInput>
          <attribute>
            <Name>Input</Name>

          </attribute>
        </DataInput>
        <DataResult>
          <attribute>
            <Name>Mode</Name>
          </attribute>
        </DataResult>
      </StatsOp>

      <StatsOp>
        <Name>median</Name>
        <Description>Returns the median value of the input numeric values.
          The median is the middle value if the numerical values are sorted into
          ascending order.</Description>
        <DataInput>
          <attribute>
            <Name>Input</Name>
          </attribute>

        </DataInput>
        <DataResult>
          <attribute>
            <Name>Median</Name>
          </attribute>
        </DataResult>
      </StatsOp>
      <StatsOp>

        <Name>standard_deviation</Name>
        <Description>Returns the standard deviation of the input numeric values.</Description>
        <DataInput>
          <attribute>
            <Name>Input</Name>
          </attribute>
        </DataInput>

        <DataResult>
          <attribute>
            <Name>StandardDeviation</Name>
          </attribute>
        </DataResult>
      </StatsOp>
      <StatsOp>
        <Name>frequency_distribution_numeric</Name>

        <Description>Returns the number of occurrences of each unique input number.
          The return values are an array of value/count pairs.</Description>
        <DataInput>
          <attribute>
            <Name>Value</Name>
          </attribute>
        </DataInput>
        <DataResult>
          <attribute>

            <Name>UniqueValue</Name>
          </attribute>
          <attribute>
            <Name>Count</Name>
          </attribute>
        </DataResult>
      </StatsOp>
      <StatsOp>

        <Name>frequency_distribution_string</Name>
        <Description>Returns the number of occurrences of each unique input strings.
          The return values are an array of value/count pairs.</Description>
        <DataInput>
          <attribute>
            <Name>Value</Name>
          </attribute>
        </DataInput>

        <DataResult>
          <attribute>
            <Name>UniqueValue</Name>
          </attribute>
          <attribute>
            <Name>Count</Name>
          </attribute>
        </DataResult>

      </StatsOp>
      <StatsOp>
        <Name>unique_count</Name>
        <Description>Returns the number of unique items in the input string list.</Description>
        <DataInput>
          <attribute>
            <Name>Value</Name>

          </attribute>
        </DataInput>
        <DataResult>
          <attribute>
            <Name>Count</Name>
          </attribute>
        </DataResult>
      </StatsOp>

      <StatsOp>
        <Name>unique_list</Name>
        <Description>Returns the list of unique string inputs.</Description>
        <DataInput>
          <attribute>
            <Name>Value</Name>
          </attribute>

        </DataInput>
        <DataResult>
          <attribute>
            <Name>UniqueValue</Name>
          </attribute>
        </DataResult>
      </StatsOp>
    </StatisticalOperations>

    <StatisticalPresentations>
      <StatsPresentation>
        <PresentationType>html_table_fragment</PresentationType>
        <DataInput>
          <DataSet/>
        </DataInput>
      </StatsPresentation>
      <StatsPresentation>

        <PresentationType>html_table_document</PresentationType>
        <DataInput>
          <DataSet/>
        </DataInput>
      </StatsPresentation>
      <StatsPresentation>
        <PresentationType>html_chart_fragment</PresentationType>
        <DataInput>

          <DataSet/>
        </DataInput>
      </StatsPresentation>
      <StatsPresentation>
        <PresentationType>html_chart_document</PresentationType>
        <DataInput>
          <DataSet/>
        </DataInput>

      </StatsPresentation>
      <StatsPresentation>
        <PresentationType>text_table</PresentationType>
        <DataInput>
          <DataSet/>
        </DataInput>
      </StatsPresentation>
    </StatisticalPresentations>

    <GeolinkedData>
      <Framework href="http://www2.dmsolutions.ca/msapps/gdas/gdas.php">
        <organization>Environment Canada</organization>
        <domain>ec.gc.ca</domain>
        <name>Ecoregion(shape)</name>
        <title>Ecoregions of Canada</title>
        <description>Ecoregions of Canada, forming part of the Terrestrial Ecological
          Stratification of Canada.</description>

        <version>1</version>
        <releasedate>1995-06-03</releasedate>
        <documentation>http://sis.agr.gc.ca/cansis/nsdb/ecostrat/region/</documentation>
        <geolinkagefield>ecoregion</geolinkagefield>
        <DataSet>
          <organization>Agriculture and Agri-Food Canada</organization>

          <domain>agr.gc.ca</domain>
          <name>1961-90ClimateNormals</name>
          <title>1961-1990 Climate Normals</title>
          <description>Climate normals determined for Terrestrial Ecological units for the
            1961 - 1990 period.</description>
          <version>1999</version>
          <releasedate>1999-04-10</releasedate>

          <documentation>http://sis.agr.gc.ca/cansis/nsdb/ecostrat/climate_normals_1961-90.html</documentation>
          <geolinkagefield>DISTRICT</geolinkagefield>
          <attribute>
            <name>TMEAN_JAN</name>
            <units>centigrade degrees</units>
            <type>interval</type>

            <title>Mean Monthly Temperature - January 1961 - 1990</title>
            <description>Mean Monthly Temperature - January 1961 - 1990</description>
            <version>1999</version>
            <releasedate>1999-04-10</releasedate>
            <documentation>http://sis.agr.gc.ca/cansis/nsdb/ecostrat/climate_normals_1961-90.html#temperature
              </documentation>
          </attribute>

          <attribute>
            <name>TMIN_JAN</name>
            <units>centigrade degrees</units>
            <type>interval</type>
            <title>Minimum Monthly Temperature - January 1961 - 1990</title>
            <description>Minimum Monthly Temperature - January 1961 - 1990</description>

            <version>1999</version>
            <releasedate>1999-04-10</releasedate>
            <documentation>http://sis.agr.gc.ca/cansis/nsdb/ecostrat/climate_normals_1961-90.html#temperature
              </documentation>
          </attribute>
          <attribute>
            <name>TMAX_JAN</name>
            <units>centigrade degrees</units>

            <type>interval</type>
            <title>Maximum Monthly Temperature - January 1961 - 1990</title>
            <description>Maximum Monthly Temperature - January 1961 - 1990</description>
            <version>1999</version>
            <releasedate>1999-04-10</releasedate>
            <documentation>http://sis.agr.gc.ca/cansis/nsdb/ecostrat/climate_normals_1961-90.html#temperature
              </documentation>

          </attribute>
          <attribute>
            <name>TMAX_FEB</name>
            <units>centigrade degrees</units>
            <type>interval</type>
            <title>Maximum Monthly Temperature - February 1961 - 1990</title>
            <description>Maximum Monthly Temperature - February 1961 - 1990</description>

            <version>1999</version>
            <releasedate>1999-04-10</releasedate>
            <documentation>http://sis.agr.gc.ca/cansis/nsdb/ecostrat/climate_normals_1961-90.html#temperature
              </documentation>
          </attribute>
          <attribute>
            <name>TMIN_FEB</name>
            <units>centigrade degrees</units>

            <type>interval</type>
            <title>Minimum Monthly Temperature - February 1961 - 1990</title>
            <description>Minimum Monthly Temperature - February 1961 - 1990</description>
            <version>1999</version>
            <releasedate>1999-04-10</releasedate>
            <documentation>http://sis.agr.gc.ca/cansis/nsdb/ecostrat/climate_normals_1961-90.html#temperature
              </documentation>

          </attribute>
          <attribute>
            <name>TMEAN_FEB</name>
            <units>centigrade degrees</units>
            <type>interval</type>
            <title>Mean Monthly Temperature - February 1961 - 1990</title>
            <description>Mean Monthly Temperature - February 1961 - 1990</description>

            <version>1999</version>
            <releasedate>1999-04-10</releasedate>
            <documentation>http://sis.agr.gc.ca/cansis/nsdb/ecostrat/climate_normals_1961-90.html#temperature
              </documentation>
          </attribute>
        </DataSet>
      </Framework>
    </GeolinkedData>

  </Capability>
</DDS_Capabilities>

DDSRequest

Request

A DDS request has three sections under a DDSRequest element. They are:

A dataset query (or instance) definition. A query may include a GetData request in a form suitable to pass on to a DAS or GDAS server. Alternatively, a Dataset data instance may be included instead of a GetData request.
A StatsOp element containing one or more Operations to apply to the data. (optional)
A StatsPresentation element defining how the datasets should be processed for presentation. (optional)

If no statistical operations are defined, the raw data will be passed on for presentation. If no presentation request is made, the data (either raw data or the output of StatsOp) will be returned in Dataset format.

In addition to the normal definitions of the GetData, StatsOp, and StatsPresentation elements from the DAS, WSA, and WSP service specifications, these elements also include an optional href attribute which, if included, indicates the server to use to satisfy the request. If no href is included, the DDS's own default configuration will determine what server to use to satisfy the request.

Examples

Example 1

Calculate the maximum value of the mean temperatures in January.

Request

<?xml version="1.0" ?>
<DDSRequest
  xmlns="http://www.someserver.com/sa"
  xmlns:xs="http://www.w3.org/2001/XMLSchema-instance"
  xs:schemaLocation="http://www.someserver.com/sa ../sa/1.0.0/SA-transaction.xsd">

  <GetData version="0.9.0" service="GDAS"
           href="http://www2.dmsolutions.ca/msapps/gdas/gdas.php">
    <Domain>ec.gc.ca</Domain>
    <Framework>
      <Name>ecodistricts</Name>
      <Version>0.9.0</Version>
    </Framework>
    <Dataset>RG_TEMP</Dataset>
    <Attribute>tempmeanjan</Attribute>
    <Attribute>rainfalljan</Attribute>
    <GeolinkIds>
      <I>1</I>
      <I>5</I>
      <I>6</I>
      <I>7</I>
      <I>8</I>
      <I>9</I>
    </GeolinkIds>
  </GetData>

  <StatsOp href="http://gdal.velocet.ca/cgi-bin/wsa">
    <Operation name="max">
      <Description>Max of some random values</Description>
      <Attribute>
        <Name>Maximum Value:</Name>
      </Attribute>
    </Operation>
  </StatsOp>

  <StatsPresentation href="http://gdal.velocet.ca/cgi-bin/wsp">
    <PresentationType>html_table_document</PresentationType>
  </StatsPresentation>
</DDSRequest>

Response

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
  <title>Statistical Presentation</title>
  <meta name="author" content="GDAS Statistical Presenter Module">
</head>
<body>
  <b>Max of some random values</b>
  <table cellpadding="2" cellspacing="2" border="1" style="text-align: left; width: 150px;">
    <tbody>
      <tr>
        <td style="vertical-align: top; background-color: rgb(204, 204, 204); text-align: center;">
          Maximum Value:
        </td>
      </tr>
      <tr>
        <td style="vertical-align: top;">
          3.700000
        </td>
      </tr>
    </tbody>
  </table>
  <br>
</body>
</html>

DDSGUI Requirements

From the Requirements Document

DDSGUI is a user interface to call the MainDDS. It can:

accept XML requests.
accept XML formatted requests via the REQUEST_BODY form variable.
allow any html template to be provided as the user interface.
allow the selection of statistical operators and output format.
return whatever is returned by the DDS Main Interface.
report any error.

DDSGUI Specification

Introduction

The DDSGUI is responsible for collecting capabilities from a Main DDS server, submitting a build request based on user selections, and then outputting what is returned by the Main DDS server. It doesn't do much actual work itself. The service request to the DDSGUI consists primarily of a request that is passed on directly to the Main DDS server, already formatted in the form appropriate to those server.

The DDSGUI server implements a GetCapabilities request and a DDSGUIRequest service.

Exceptions

The returned exception should always have the mime type text/xml.

Example

The following is an example of an exception report. This exception indicates that a mandatory tag is missing.

<?xml version="1.0" ?>
<ServiceExceptionReport version="1.1.0">
  <ServiceException>
    OriginServerURI, OriginServerField and GeolinkIds needed to request the DDS server.
  </ServiceException>
</ServiceExceptionReport>

It should be noted that this sample output validates against the exception report schema presented above.

GetCapabilities Operation

Each DDSGUI Server must describe its capabilities. This clause defines an XML document structure intended to convey general information about the service itself.

GetCapabilities Request

Key-value Pair Encoding

The following keywords are defined for KeyValuePair requests:

Table 3. KeyValuePair Requests - DDSGUI

Request Parameter	Required/Optional	Description
`REQUEST=GetCapabilities`	Required	Request Name
`VERSION=0.1.0`	Optional	Request Version
`SERVICE=DDSGUI`	Required	Service Type

The VERSION and SERVICE parameters, respectively, denote the version number of the specification and the service it addresses. For DDSGUI requests, the SERVICE parameter must have the value "DDSGUI".

XML Encoding

XML encoded GetCapabilities requests take the following form:

Table 4. XML Encoded GetCapabilities Requests - DDSGUI

Attribute	Required/Optional	Description
`version`	Optional	Request version. Defaults to the latest available version, currently 0.1.0
`service`	Required	Service Type, must be DDSGUI

For example, a client may encode a GetCapabilities request in XML as follows:

<GetCapabilities version="0.1.0" service="DDSGUI" />

GetCapabilities Response

Description

The DDSGUI GetCapabilities only describes the requests that are available for the server. It does not tell much, because it does not do much. It is simply an interface to using a Main DDS server.

DDSGUIRequest

Request

A DDSGUI request has three elements under a DDSGUIRequest element. They are OriginServerURI, OriginServerField, and GeolinkIds. Those elements are passed to the Main DDS Interface GetCapabilities request. From there, an HTML page is output, where the user can select which operations and output format are desired.

Examples

Example 1

Request to a Main DDS server. Note: This will be passed through the REQUEST_BODY form element via the POST method.

Request

<?xml version="1.0" ?>
<DDSGUIRequest version="0.9.0">
<OriginServerURI>http://www.maptools.org/cgi-bin/wms</OriginServerURI>
  <OriginServerField>FID</OriginServerField>
  <GeolinkIds>
    <I>1</I>
    <I>3</I>
    <I>6</I>
  </GeolinkIds>
</DDSGUIRequest>

HTML template

<html>
<body>

<br>
<form method=POST>
<DDSGUI Attributes Multiple><br>
<DDSGUI StatsOp Size="4" Multiple><br>
<DDSGUI OutputFormat Multiple><br>
<br>

<input type="submit" name="DDSGUI_SUBMIT" value="Go!">
</form>

</body>
</html>

Response

<html>
<body>

<br>
<form method=POST>
<input type="hidden" name="DDSGUIGeolinkIds" value="1">
<input type="hidden" name="DDSGUIGeolinkIds" value="3">
<input type="hidden" name="DDSGUIGeolinkIds" value="6">
<input type="hidden" name="DDSGUIFrameworkName" value="Ecoregion(shape)">
<input type="hidden" name="DDSGUIFrameworkHREF" value="http://www2.dmsolutions.ca/msapps/gdas/gdas.php">
<input type="hidden" name="DDSGUIVersion" value="1">
<input type="hidden" name="DDSGUIDataSet" value="1961-90ClimateNormals">
<Select Name="DDSGUIAttribute"  Multiple>
  <option>TMEAN_JAN</option>
  <option>TMIN_JAN</option>

  <option>TMAX_JAN</option>
  <option>TMAX_FEB</option>
  <option>TMIN_FEB</option>
  <option>TMEAN_FEB</option>
</Select>
<br>
<Select Name="DDSGUIStatsOp"  Size="4" Multiple>
  <option value="mean&Computes the Euclidean mean of the given numeric values -
  by summing and dividing by the value count&Mean">mean</option>

  <option value="min&Returns the minimum value of the input numeric
    values&Minimum">min</option>
  <option value="max&Returns the maximum value of the input numeric
    values&Maximum">max</option>
  <option value="mode&Returns the mode value of the input numeric values.
    The mode is the most frequently occurring input value.&Mode">mode</option>
  <option value="median&Returns the median value of the input numeric values.
    The median is the middle value if the numerical values are sorted into ascending
    order.&Median">median</option>
  <option value="standard_deviation&Returns the standard deviation of the
    input numeric values.&StandardDeviation">standard_deviation</option>
  <option value="frequency_distribution_numeric&Returns the number of
    occurrences of each unique input number.  The return values are an array of
    value/count pairs.&UniqueValue">frequency_distribution_numeric</option>

  <option value="frequency_distribution_string&Returns the number of
    occurrences of each unique input strings.  The return values are an array of
    value/count pairs.&UniqueValue">frequency_distribution_string</option>
  <option value="unique_count&Returns the number of unique items in
    the input string list.&Count">unique_count</option>
  <option value="unique_list&Returns the list of unique string
    inputs.&UniqueValue">unique_list</option>
</Select>
<br>
<Select Name="DDSGUIOutputFormat"  Multiple>
  <option>html_table_fragment</option>
  <option>html_table_document</option>

  <option>html_chart_fragment</option>
  <option>html_chart_document</option>
  <option>text_table</option>
</Select>
<br>
<br>

<input type="submit" name="DDSGUI_SUBMIT" value="Go!">
</form>

</body>
</html>

About this Document

Copyright/Licensing Information

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Feedback

Send any comments or suggestions to the author.