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

Re: THREDDS Catalog Generator Error



Hi Mark,

Yeah, this is a bit weird. Your config file and the resulting file look fine.
They are both InvCatalog documents. The result doc has nested datasets, the leaf
datasets are accessible because they refer to <service> elements. The config
file contains only one dataset that does not refer to a <service> element but
contains a metadata record. The parser is spitting out this warning message
because it is treating the config file like an InvCatalog doc and the parser
thinks a dataset without child datasets or a reference to a service may be a
problem.

So, bottom line, the warning is something you should ignore.

Does that make sense?

Ethan

Mark A Ohrenschall wrote:
> 
> Hi Ethan,
> 
> Okay, this is working a lot nicer now. However, I'm confused about there being
> no service and no child datasets. I copied the example from
> http://www.unidata.ucar.edu/projects/THREDDS/tech/cataloggen/CatalogGenConfig.html
> and just changed some of the particulars -- we are indeed running a DODS
> server through which these datasets are accessible (is the <resultservice> tag
> not filled properly?) and I'm not sure what nested datasets mean (the
> generated catalog .xml file has nested <dataset> tags...).
> 
> address@hidden THREDDS]$ /usr/java/j2sdk1.4.1_02/bin/java -classpath 
> cataloggen-0.6.jar:thredds.jar:jdom-b8.jar:dods.1.1.1.jar 
> thredds.cataloggen.CatalogGen file:///home/mao/THREDDS/mytest.xml
> readMetadataContent=[Element: <catalogGenConfig [Namespace: 
> http://www.unidata.ucar.edu/thredds]/>]
> Catalog read successfully (file:///home/mao/THREDDS/mytest.xml):
> Message=----Catalog Validation version 0.6.02
>   **Dataset (3) (my collection): is not selectable and does not have nested 
> datasets
> 
> <?xml version="1.0" encoding="UTF-8"?>
> <!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"; name="my test" version="0.6">
>   <dataset name="my collection" dataType="Grid">
>     <service name="myserver" serviceType="DODS" 
> base="http://panther.ngdc.noaa.gov/cgi-bin/dods/nph-dods/"; />
>     <dataset name="dods/processing" serviceName="myserver">
>       <dataset name="My Test ow" urlPath="dods/processing/ow.nc" />
>     </dataset>
>     <dataset name="My Test ow" serviceName="myserver" urlPath="dods/ow.nc" />
>     <dataset name="My Test lw" serviceName="myserver" urlPath="dods/lw.nc" />
>   </dataset>
> </catalog>
> 
> address@hidden THREDDS]$ cat mytest.xml
> <?xml version="1.0" encoding="UTF-8"?>
> <!-- edited with XML Spy v4.3 U (http://www.xmlspy.com) by Mark Ohrenschall 
> (US Dept of Commerce/NOAA/NESDIS) -->
> <!DOCTYPE catalog SYSTEM 
> "http://www.unidata.ucar.edu/projects/THREDDS/xml/CatalogGenConfig.0.5.dtd";>
> <catalog name="my test" version="0.6">
>   <dataset name="my collection" dataType="Grid">
>     <metadata metadataType="CatalogGenConfig">
>       <catalogGenConfig type="Catalog">
>         <datasetSource name="ds source" type="Local" structure="DirTree" 
> accessPoint="/data/www/html/dods/">
>           <resultService name="myserver" serviceType="DODS" 
> base="http://panther.ngdc.noaa.gov/cgi-bin/dods/nph-dods/"; 
> accessPointHeader="/data/www/html/"/>
>           <datasetNamer name="My Test" type="RegExp" addLevel="false" 
> matchPattern="(..)\.nc$" substitutePattern="My Test $1"/>
>           <datasetFilter name="My Test" type="RegExp" 
> matchPattern="\/.w\.nc$"/>
>         </datasetSource>
>       </catalogGenConfig>
>     </metadata>
>   </dataset>
> </catalog>
> address@hidden THREDDS]$
> 
> Thanks,
> 
> Mark

-- 
Ethan R. Davis                       Telephone: (303) 497-8155
Software Engineer                    Fax:       (303) 497-8690
UCAR Unidata Program Center          E-mail:    address@hidden
P.O. Box 3000
Boulder, CO  80307-3000              http://www.unidata.ucar.edu/

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.