Upgrading To TDS 4.0
- A WMS data service has been added (thanks to Jon Blower and Pauline Mak, the ncWMS
developers). Use like WCS, by adding a WMS service to your catalog, and
giving your gridded datasets that service.
<service name="wms" serviceType="WMS" base="/thredds/wms/" />
<dataset name="my gridded dataset" urlPath="so/cool/data.nc" >
<serviceName>wms</serviceName>
</dataset>
You must also explicitly enable the WMS service in threddsConfig.xml:
<WMS>
<allow>true</allow>
<paletteLocationDir>palettes</paletteLocationDir>
...
</WMS>
See THREDDS Web Map Service for complete details. Be sure to add the JVM option if running on a Unix machine.
More detail on explicitly enabling services in the TDS Reference for each individual service. The following services must be explicitly enabled in the threddsConfig.xml file:
- WCS (required explicit allow since 3.16)
- WCS for remote datasets (required explicit allow since 3.17)
- WMS: general allow and allow for remote datasets.
- Catalog Services on remote catalogs (requires explicit allow as of 4.0)
- Less common services:
- DLwriter (requires explicit allow as of 4.0)
- DLwriter on remote catalogs (requires explicit allow as of 4.0)
- Deprecated services (as of 4.0):
- CatalogGen (requires explicit allow as of 4.0)
- DqcService (requires explicit allow as of 4.0)
As of TDS 4.0.12,
binary (".dods") and ASCII (".asc") OPeNDAP requests are being
restricted depending on the size of the response body. By default, the
size limit on the binary response is 500Mbytes and on the ascii
response is 50Mbytes. Details on configuring these size limits are
available here.
If a binary
OPeNDAP request will result in a response body larger than the
configured limit
or an ASCII OPeNDAP request will result in a response body larger than
the configured limit, the request will not be handled. Instead an HTTP
status code
of 403 (Forbidden) is returned with a "dods-error" response body.
As of
TDS 4.0, the CDM Coordinate System validator is no longer available as
part of the TDS. It is available as a separate web application
distributed in its own .war file.
System requirements are the same as for the TDS.
Download information is also available on the
TDS page.
TDS 4.0 gives you more control over the HTML pages generated by TDS. Some information you can configure in the threddsConfig.xml file:
- Standard CSS document to use.
- CSS document for HTML catalog view pages.
- Name, URL, and logo for your TDS installation (optional).
- Name, URL, and logo for the institution at which you are running your TDS installation (optional).
The following is an example from one of our TDS installations:
<htmlSetup>
<cssPage>tds.css</cssPage>
<cssCatalog>tdsCat.css</cssCatalog>
<folderIconUrl>folder.gif</folderIconUrl>
<folderIconAlt>Folder</folderIconAlt>
<datasetIconUrl>dataset.gif</datasetIconUrl> <!-- Not currently used. -->
<datasetIconAlt>Dataset</datasetIconAlt> <!-- Not currently used. -->
<installName>Motherlode TDS</installName>
<installLogoUrl>unidataLogo.gif</installLogoUrl>
<installLogoAlt>Motherlode TDS</installLogoAlt>
<hostInstName>Unidata</hostInstName>
<hostInstUrl>http://www.unidata.ucar.edu/</hostInstUrl>
<hostInstLogoUrl>unidataLogo.gif</hostInstLogoUrl>
<hostInstLogoAlt>Unidata</hostInstLogoAlt>
</htmlSetup>
NOTE:
URLs may be absolute or relative, relative URLs must be
relative to the webapp URL, i.e., http://server:port/thredds/.
Catalog services include HTML views, subsetting, and validation of catalogs. These services have been simplified in TDS 4.0.
The URL to access TDS remote management is now
https://server:port/thredds/admin/debug
In TDS 3.16/3.17, it was https://server:port/thredds/debug. Note that
this is available only under SSH, which you must
enable.
This document is maintained by Unidata and was
last updated June 09, 2009. Send comments to THREDDS
support.
