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.
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.
Yes, that is exactly what I tell you in my E-mail. The URL does not work with met.no, I have to use metno instead. But the first URL (with met.no) worked fine in TDS 4.3, and it does not in 4.6. Why? We have a large number of hardcoded URLs using met.no which we prefer not to change, although this will be an achievable task. But I do not want to do this before I know the reason for the difference between 4.3 and 4.6. Is this a documented change or a bug? Best regards, Egil On Wed, Jun 29, 2016 at 6:52 PM, dmh@xxxxxxxx <dmh@xxxxxxxx> wrote: > If you change 'met.no' in that url to 'metno' > it works. > =Dennis Heimbigner > Unidata > > On 6/29/2016 4:35 AM, Egil Støren wrote: > >> 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 <http://met.no>" >> location="/metno/damocles/arcticdata/met.no/ <http://met.no/>"> >> ... >> </datasetScan> >> >> While the above URL does not work, the following URL will work (where >> "?dataset=arcticdata/met.no/.. <http://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 >> >> >> _______________________________________________ >> NOTE: All exchanges posted to Unidata maintained email lists are >> recorded in the Unidata inquiry tracking system and made publicly >> available through the web. Users who post to any of the lists we >> maintain are reminded to remove any personal information that they >> do not want to be made public. >> >> >> thredds mailing list >> thredds@xxxxxxxxxxxxxxxx >> For list information or to unsubscribe, visit: >> http://www.unidata.ucar.edu/mailing_lists/ >> >>
thredds archives: