TDS Catalog Services


Catalog Services for Local TDS Served Catalogs

The path of the request URL identifies the target catalog. The extension on the filename determines whether an XML or HTML view is returned, ".xml" or ".html" respectively.

Subsetting of the catalog is performed if a dataset parameter is included in the request. The value of the dataset parameter must match the ID of a dataset in the target catalog.

Examples

The following returns an HTML view of the main TDS catalog on motherlode:

http://motherlode.ucar.edu:8080/thredds/catalog/catalog.html
The following returns an HTML view of one of the datasets from the same catalog:
http://motherlode.ucar.edu:8080/thredds/catalog/galeon/testdata/catalog.html?dataset=galeon/testdata/GFS_Global_5x2p5deg.nc


Catalog Services for Remote Catalog

Catalog services on remote catalogs are only allowed if the following is added to the threddsConfig.xml configuration file:

<CatalogServices>
<allowRemote>true</allowRemote>
</CatalogServices>

Catalog services for remote catalogs are requested from the following URL:

http://myserver/thredds/remoteCatalogService

The following parameters are recognized:

A few notes on the above parameters:

The action performed for each value of the "command" parameter are as follows:

Catalog subsetting is done on the logical structure of the catalog rather than directly on the XML. This means that all service elements are included in the catalog and all metadata inherited by the target dataset are included in the resulting dataset.

Examples

The following returns an HTML view of a catalog on s

http://myserver/thredds/remoteCatalogService?catalog=http://otherServer/whatever/catalog.xml

The following returns an HTML view of one of the datasets from the same catalog:

http://myserver/thredds/remoteCatalogService?catalog=http://otherServer/whatever/catalog.xml&dataset=path/datasetID

THREDDSThis document is maintained by Unidata and was last updated April 2015. Send comments to THREDDS support.