Re: [thredds] Wrong mapping from catalog to dataset in some cases?

I just made a test with a 3.16 thredds server:

http://thredds.met.no/thredds/catalog/data/met.no/hirlam12/
from the 4.0 server gives wrong dataset-links, while
http://damocles.met.no:8080/thredds/catalog/data/met.no/hirlam12/
from the 3.16 server gives the correct dataset-links.

Both servers use identical catalog.xml files (from the same NFS-server) with the element:
<datasetScan name="hirlam12" ID="met.no/hirlam12"
   path="data/met.no/hirlam12" location="...">

Heiko

Heiko Klein wrote:
Hi,

I'm using thredds 4.0.25 and have some problems in getting the correct mapping between the catalog-view and the dataset view.

I have i.e. two datasetScans:

<datasetScan name="Nordic4 model data" path="nordic4b" location="..." serviceName="all">

and

<datasetScan name="ice" ID="met.no/ice"
               path="osisaf/met.no/ice" location="...">


The nordic4 catalog at
http://thredds.met.no/thredds/catalog/nordic4b/ gives me correct dataset-links as: http://thredds.met.no/thredds/catalog/nordic4b/catalog.html?dataset=nordic4b/mipom_nordic4.fc.20091209.nc

The ice catalog at
http://thredds.met.no/thredds/catalog/osisaf/met.no/ice/ gives me wrong (HTTP 404 - Not found) dataset-links as: http://thredds.met.no/thredds/catalog/osisaf/met.html?dataset=met.no/ice/ice_conc_nh_200911261200_CF.nc

Appending 'catalog.html' to the ice catalog gives me the correct dataset-links as: http://thredds.met.no/thredds/catalog/osisaf/met.no/ice/catalog.html?dataset=met.no/ice/ice_conc_nh_200911261200_CF.nc

Is there something wrong in my setup, or is thredds translating the dataset-pathes wrong if there are several 'subdirectories' in the path-element?


Best regards,

Heiko




  • 2009 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the thredds archives: