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

Re: Thredds init error

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: Re: Thredds init error
  • Date: Mon, 12 Jun 2006 17:23:53 -0600
Hi Bruce,
I suspect that with your upgrade to TDS 3.10 that you will still get the error messages you listed but that the TDS should work as desired. As I mentioned, the TDS keeps track of a datasetScan/datasetRoot for each unique path. If it finds a duplicate, it writes the error message (it will be a warning in our next release) and continues. Doesn't look like the duplication should cause any trouble. 

From your content/thredds/catalog.xml

   <datasetScan dirLocation="/Volumes/gulf1/Shelves/"
                path="Shelves" name="Shelves" serviceName="other">
From your content/thredds/dodsC/Modeled_Data/Fulldisk8km/Profiles/Oct05/2003_0624_1800/catalog.xml 

   <service name="group" base="" serviceType="Compound" >
       <service name="dods" base="/thredds/dodsC/" serviceType="OpenDAP" />
<service name="http" base="/thredds/fileServer/" serviceType="HTTPServer" /> 
       <datasetRoot path="Shelves" dirLocation="/Volumes/gulf1/Shelves/"/>
   </service>
      ...
<dataset name="8km_0624_2003.1800utc_10_3.nc" ID="aa057bd8-2104-44ee-bef7-51859bac9627-8km_0624_2003.1800utc_10_3.nc" > 
           ...
<access urlPath="Shelves/aa05/7bd8/aa057bd8-2104-44ee-bef7-51859bac9627/8km_0624_2003.1800utc_10_3.nc" serviceName="group" /> 
       </dataset>
One thing you could do to get rid of this duplication ... If all the access urlPaths in each catalog are the same except for the final dataset name, you could put the whole thing in your datasetRoot path. So, in the above example you could instead have: 

   <service name="group" base="" serviceType="Compound" >
       <service name="dods" base="/thredds/dodsC/" serviceType="OpenDAP" />
<service name="http" base="/thredds/fileServer/" serviceType="HTTPServer" /> <datasetRoot path="Shelves/aa05/7bd8/aa057bd8-2104-44ee-bef7-51859bac9627" dirLocation="/Volumes/gulf1/Shelves/aa05/7bd8/aa057bd8-2104-44ee-bef7-51859bac9627/"/> 
   </service>
      ...
<dataset name="8km_0624_2003.1800utc_10_3.nc" ID="aa057bd8-2104-44ee-bef7-51859bac9627-8km_0624_2003.1800utc_10_3.nc" > 
           ...
<access urlPath="Shelves/aa05/7bd8/aa057bd8-2104-44ee-bef7-51859bac9627/8km_0624_2003.1800utc_10_3.nc" serviceName="group" /> 
       </dataset>

But I think the only advantage would be cleaning up your log files.

Hope this makes sense.

Ethan

--
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/
---------------------------------------------------------------------------


===============================================================================
To unsubscribe thredds, visit:
http://www.unidata.ucar.edu/mailing-list-delete-form.html
===============================================================================