Hi,
We have recently upgraded from TDS 4.3 to TDS 4.6, and discover that some
dataset URLs that formerly worked OK, no gives 404 Not found status.
One example is this:
http://thredds.met.no/thredds/catalog/arcticdata/met.no/tamHADA2HI55NO/catalog.html?dataset=arcticdata/met.no/tamHADA2HI55NO/tamHADA2HI55NO_2090_01_01.nc
This dataset is part of a datasetscan element in the catalog:
<datasetScan name="MET Norway" ID="arcticdata/metno" path="arcticdata/met.no"
location="/metno/damocles/arcticdata/met.no/">
...
</datasetScan>
While the above URL does not work, the following URL will work (where
"?dataset=arcticdata/met.no/..." is replaced with
"?dataset=arcticdata/metno/..."):
http://thredds.met.no/thredds/catalog/arcticdata/met.no/tamHADA2HI55NO/catalog.html?dataset=arcticdata/metno/tamHADA2HI55NO/tamHADA2HI55NO_2090_01_01.nc
It seems that TDS use the ID attribute in the datasetscan element to
construct the dataset path rather than the path attribute. But I find this
hard to believe, as it would surely have been discovered already by others.
Can anyone provide an explanation?
Best regards,
Egil Støren
MET Norway
