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

Re: wrestling with new server

Tennessee Leeuwenburg wrote:
Hi all,

I am struggling with getting the new server working. The datasetScan is
working great, but I can't seem to publish specific files.

What I have are two files which I want to publish. One of those files is
at /data/pymars/bufr_conversion_samples/AVHRR_SST_v1.nc. The other one
is at http://localhost:8040/mars/start_request/300/end_request/300.nc.

When I attempt to configure these in, I see entries in the catalog, but
they are not click-able. It's like thredds is setting these up as
datasets, but not noticing that they are actually individual files.

I am using thredds v3.0.


Hi Tennessee :

First, switch to the 3.2 release.

Second, the datasets need to have an ID to be selectable from the HTML 
interface. The datasetScan will automatically add these.

<?xml version="1.0" encoding="UTF-8"?> <catalog xmlns="http://www.unidata.ucar.edu/namespaces/thredds/InvCatalog/v1.0"; xmlns:xlink="http://www.w3.org/1999/xlink"; name="Test Data Catalog for NetCDF-OPeNDAP Server" version="1.0.1">

  <service name="myserver" serviceType="Compound" base="">
    <service name="ncdods" serviceType="OpenDAP" base="/thredds/dodsC/"/>
    <service name="HTTPServer" serviceType="HTTPServer"
    <service name="WCS" serviceType="WCS" base="/thredds/wcs/"/>
    <datasetRoot path="mars" dirLocation="http://linux-dev:8040/mars/"/>

  <!--service name="myserver" serviceType="OpenDAP" base=""/-->
  <service name="latest" serviceType="Resolver" base="" />

  <service name="bufr" serviceType="OpenDAP" base="/thredds/dodsC/">
    <datasetRoot path="bufr_conversion_samples"
  <dataset name="foo" serviceName="bufr"

  <dataset name="foo2" path="buf" dirLocation="/data/pymars/"

<datasetScan name="Data" path="testRelative" dirLocation="/data/pymars/" filter=".*nc$"> <metadata inherited="true"> <serviceName>myserver</serviceName> </metadata> </datasetScan>


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.