Hi Nathan,
Here's the reference doc for TDS 4.x:
> http://www.unidata.ucar.edu/Projects/THREDDS/tech/tds4.0/reference/CatalogService.html
And here's a validation URL that works for your catalog:
> http://motherlode.ucar.edu:8080/thredds/catalogServices?command=validate&verbose=true&catalog=http://206.125.94.252:8080/opendap/data/nc/catalog.xml
Ethan
On 2/9/2010 3:12 PM, Nathan Potter wrote:
>
>
> Ethan,
>
> I want to validate the THREDDS catalog output of my server.
>
> I looked here:
>
> http://www.unidata.ucar.edu/Projects/THREDDS/tech/reference/CatalogService.html
>
>
> And I tried this:
>
> http://motherlode.ucar.edu:8080/thredds/catalogServices?cmd=validate&debug=true&catalog=http://206.125.94.252:8080/opendap/data/nc/catalog.xml
>
>
> Which returned an HTML presentation of the catalog but no debugging
> information. At this point I am guessing that any debugging output for
> my catalog is living in the TDS output logs on motherlode.ucar.edu
>
> Is there another validation service that returns more information that I
> might use? Or is the solution for me to run my own TDS and use it to
> validate catalogs from my THREDDS service?
