So it is a feature and not a bug. Anyway, thanks for the explanation.
Egil
On 07/10/2013 05:57 PM, Marcos Hermida wrote:
Hi Egil,
this has to do with how TDS handles internally the datasets and how the
urls for accessing the datasets are built.
Basically, when you define your dataset in your catalogs you provide a
"path" that will be used internally as key for finding the dataset
object (actually, it also maps to the directory containing the data for
the dataset). Then, that path is provided in the urls and TDS is able to
extract it and locate the right data directory for the dataset.
In your url:
http://thredds.met.no/thredds/wms/myocean/siw-tac/siw-metno-glo-osisaf/drift/2011/10/ice_drift_nh_polstere-625_multi-oi_201110251200-201110271200.nc?service=WMS&version=1.3.0&request=GetCapabilities
the path would be: myocean/siw-tac/siw-metno-glo-osisaf. TDS uses what
is between that and the query string for locating the right file and it
ignores the "/". So, it'll use:
drift/2011/10/ice_drift_nh_polstere-625_multi-oi_201110251200-201110271200.nc
as relative path to the directory containing the data, regardless you
have put the "/" after the path or not in your url and urls without "/"
after the path should work fine, although is a bit obscure and those
urls without the slash don't represent quite well the resource in the
server.
Hope it clarifies...
Cheers!
On 07/10/2013 03:34 AM, Egil Støren wrote:
Hi all,
We discovered a peculiar feature/bug related to URLs for WMS
getcapabilities documents in TDS 4.3.17.
This URL:
http://thredds.met.no/thredds/wms/myocean/siw-tac/siw-metno-glo-osisaf/drift/2011/10/ice_drift_nh_polstere-625_multi-oi_201110251200-201110271200.nc?service=WMS&version=1.3.0&request=GetCapabilities
gives the expected result.
If we in the above URL removes the '/' between 'siw-metno-glo-osisaf'
and 'drift', like this:
http://thredds.met.no/thredds/wms/myocean/siw-tac/siw-metno-glo-osisafdrift/2011/10/ice_drift_nh_polstere-625_multi-oi_201110251200-201110271200.nc?service=WMS&version=1.3.0&request=GetCapabilities
we get a very similar result. The only difference is that the paths
inside the document is updated to the erroneous path in the URL.
This same behaviour can also be seen on motherlode:
http://motherlode.ucar.edu/thredds/wms/grib/NCEP/GFS/Global_0p5deg/files/GFS_Global_0p5deg_20130706_1800.grib2?service=WMS&version=1.3.0&request=GetCapabilities
vs.
http://motherlode.ucar.edu/thredds/wms/grib/NCEP/GFS/Global_0p5degfiles/GFS_Global_0p5deg_20130706_1800.grib2?service=WMS&version=1.3.0&request=GetCapabilities
Explanation?
Best regards,
Egil Støren
met.no
_______________________________________________
thredds mailing list
thredds@xxxxxxxxxxxxxxxx
For list information or to unsubscribe, visit:
http://www.unidata.ucar.edu/mailing_lists/
