NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.

To learn about what's going on, see About the Archive Site.

Re: Newbie problems with catalog generator

Tennessee Leeuwenburg wrote:


Ethan Davis wrote:


Hi Tennessee,

Did you edit the config.xml file (which sets up the tasks) as well as
the cat gen config file? I guess you must have if it is showing up in
the interface. Make sure the period value is not set to zero; if it
is, the task won't be run. Are you getting any messages in the log
files? What version of the server are you running? Is this a publicly
available server? If so, send me the URL and I'll take a look at the
config files.

Sorry these config file formats are so ugly. We're working on
simplifying and cleaning up the configuration throughout the server.
But for now ...


Well, as long as you're willing to help me, ugly is fine :)
More than willing to help. But I want simpler because it would make it easier for me to remember what is going on :) 


After making that change, the server started to process the various
files. The exampls DODS catalog was generated fine, the example
filesystem catalog and my own filesystem catalog both failed with
similar messages. I've appended the results.

I think I'm failing to understand what exactly the serviceName, base and
accessPointHeader are actually used for.

As with regular catalogs, I assume one is used for reconstructing the
URL to the file to be resourced, and the other is used for constructing
the URL to be used in an OpenDAP request, but it's not clear to me
exactly what is happened. I read the documentation, but it was a bit
hand-wavy about the specifics.
The accessPoint is the directory that is to be scanned for data files. The accessPointHeader is a parent directory of the accessPoint directory and is used to remove the part of the data file path that is not to appear in the resulting dataset access URL. The base value is the URL for the OPeNDAP server that is serving your data. For instance, if you want to crawl the /my/data/radar/level3/FTG directory and a resulting dataset access URL is something like http://.../nph-dods/radar/level3/FTG/file.nc, you would want something like 

<datasetSource name="model data source" type="Local" structure="Flat"
                        accessPoint="/my/data/radar/level3/FTG">
<resultService name="mlode" serviceType="DODS" base="http://.../nph-dods/"; 
                             accessPointHeader="/my/data/"/>
       <datasetFilter ... />
       <datasetNamer ... />
</datasetSource>
Does that clear things up at all? If not, feel free to send me your config file to look at.
Sorry about the documentation. It isn't all that clear and I haven't put much effort into it since we decided to move to a simpler config file format. Not sure what's up below with the example file system dataset. I must have broken something at some point. 

What version of the cat gen servlet (or THREDDS server) are you running?

Ethan
PS In the new TDS, catalogs for the data it is serving are automatically generated and the config files are much simpler than these. 
Thanks for your help,
-T

<catalog name="THREDDS CatalogGen test config file" version="0.6">
−
<dataset name="THREDDS CatalogGen test config file">
<service name="linuxdev" serviceType="DODS"
base="http://localhost:8010/thredds/cataloggen/"/>
<service name="mlode" serviceType="DODS"
base="http://localhost:8080/thredds/cataloggen/"/>
−
<dataset name="NCEP Eta 80km CONUS model data">
<dataset name="The DatasetSource "Local Disk Data Sets" could not be
expanded. The accessPointHeader
(/home/tjl/jakarta-5.0.28/content/thredds/cataloggen/) is not a
directory." serviceName="linuxdev"/>
</dataset>
−
<dataset name="NCEP GFS 80km CONUS model data">
<dataset name="The DatasetSource "model data source" could not be
expanded. The accessPointHeader (./content/thredds/cataloggen/) is not a
directory." serviceName="mlode"/>
</dataset>
</dataset>
</catalog>


--
Ethan R. Davis                                Telephone: (303) 497-8155
Software Engineer                             Fax:       (303) 497-8690
UCAR Unidata Program Center                   E-mail:    edavis@xxxxxxxx
P.O. Box 3000
Boulder, CO  80307-3000                       http://www.unidata.ucar.edu/
---------------------------------------------------------------------------
  • 2005 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the thredds archives: