[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: THREDDS Catalog Validator



Hi Hongjun,
    I might add that I did that modification for you in the xml file that is posted on dataportal, you should be able to retrieve it by
pointing your IE browser to http://dataportal.ucar.edu/xml/ucar/cgd/cas.ctx or using netscape and doing "view source".
thanks, Luca

Ethan Davis wrote:
Hi Hongjun,

Hongjun Zhang wrote:
To whom it may concern,

I tried to validate my own catalog xml file using Catalog Validator
(http://motherlode.ucar.edu:8080/validation/CatalogValidation.html).
My xml file:
http://www.cgd.ucar.edu/cas/catalog/satellite/isccp/netCDF/example.ctx

The resule that I got is as below:

------------
THREDDS Catalog Validation Page Results

Catalog
http://www.cgd.ucar.edu/cas/catalog/satellite/isccp/netCDF/example.ctx

is Valid

----Catalog Validation version 0.6.02

**Dataset (3) (Example CGD/CAS/ISCCP datasets/ISCCP.199502.T42.nc): is not
selectable and
does not have nested datasets

**Dataset (3) (Example CGD/CAS/ISCCP datasets/ISCCP.CLM.T42.nc): is not
selectable and
does not have nested datasets

**Dataset (3) (Example CGD/CAS/ISCCP datasets/ISCCP.SFCFLUX.nc): is not
selectable and
does not have nested datasets

------------

My question are what the last several sentences mean, whether I need to and how
to change my xml file for these error messages.

Looks like you need to add a 'serviceName="NetCDF"' attribute to each of those
datasets (or to their parent dataset [from which they would each inherit that
serviceName]).

As it stands, the document is valid but there is no way to do anything with the
three datasets. They don't have any associated access methods ("selectable") nor
do they contain child datasets.

There are a variety of ways to associate access methods to each dataset and to
confuse the matter even more there is the scope of the service elements and the
inheritance of the serviceName attribute. In your case, just adding the
serviceName attribute to each of the datasets is probably the easiest route.

Hope that makes sense,

Ethan

Below is my xml file:

<?xml version='1.0' ?>
<!DOCTYPE catalog SYSTEM
'http://www.unidata.ucar.edu/projects/THREDDS/xml/InvCatalog.0.6.dtd'>
<catalog xmlns="http://www.unidata.ucar.edu/thredds"
xmlns:xlink="http://www.w3.org/1999/xlink" version="0.6" name="Test catalog">
<!--documentation xlink:href="" class="moz-txt-link-rfc2396E" href="http://www.ccsm.ucar.edu/index.html">"http://www.ccsm.ucar.edu/index.html"
xlink:show="new" xlink:title="CCSM home page">
Please visit the CCSM project home page for further details about the CCSM
modeling initiative
</documentation-->
<dataset name="Example CGD/CAS/ISCCP datasets">
& lt;service base="http://www.cgd.ucar.edu/cas/catalog/satellite/isccp/netCDF/"
serviceType="NetCDF" name="NetCDF" />
<dataset urlPath="ISCCP.199502.T42.nc" name="ISCCP.199502.T42.nc">
<metadata metadataType="NetCDF"
xlink:href=""moz-txt-link-freetext" href="http://www.cgd.ucar.edu/cas/catalog/satellite/isccp/netCDF/ISCCP.199">http://www.cgd.ucar.edu/cas/catalog/satellite/isccp/netCDF/ISCCP.199
502.T42.xml" />
</dataset>
<dataset urlPath="ISCCP.CLM.T42.nc" name="ISCCP.CLM.T42.nc">
<metadata metadataType="NetCDF"
xlink:href=""moz-txt-link-freetext" href="http://www.cgd.ucar.edu/cas/catalog/satellite/isccp/netCDF/ISCCP.CLM">http://www.cgd.ucar.edu/cas/catalog/satellite/isccp/netCDF/ISCCP.CLM
.T42.xml" />
</dataset>
<dataset urlPath="ISCCP.SFCFLUX.nc" name="ISCCP.SFCFLUX.nc"& gt;
<metadata metadataType="NetCDF"
xlink:href=""moz-txt-link-freetext" href="http://www.cgd.ucar.edu/cas/catalog/satellite/isccp/netCDF/ISCCP.SFC">http://www.cgd.ucar.edu/cas/catalog/satellite/isccp/netCDF/ISCCP.SFC
FLUX.nc" />
</dataset>
</dataset>
</catalog>

Thanks a lot for all your help!

Hongjun

------------------------------------------------
Hongjun Zhang
Climate and Global Dynamics Division/CAS Section
phone: (303) 497-1384 (office)
fax : (303) 497-1333
email: address@hidden
------------------------------------------------



NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.