http://motherlode.ucar.edu:8088/thredds/wcs/testdata/striped.nc
http://motherlode.ucar.edu:8088/thredds/wcs/testdata/sst.nc
http://motherlode.ucar.edu:8088/thredds/wcs/testdata/RUC.nc
I think I have fixed the first round of bugs, so please try again.
There is a slight problem in the capabilities documents. The onlineResource URLs
do not end in '?' or '&' as is mandatory in the spec (section 6.3.1 again).
However, that section also recommends that clients be prepared for just such a
case. Our client is, or at least it is *now*.
The RUC.nc service returns GeoTIFF-s with extents much bigger than the world. Is it really
an EPSG:4326 dataset? The RectifiedGrid/origin/pos from this request
http://motherlode.ucar.edu:8088/thredds/wcs/testdata/RUC.nc?REQUEST=DescribeCoverage&SERVICE=WCS&VERSION=1.0.0&COVERAGE=Geopotential_height
suggests otherwise.
Finally, the 0 to 360 range doesn't seem to be a problem - at least for our
client - because the result of the request, below, is a GeoTIFF with coords in
the -180 to 180 range, and we trust that. I must admit to being a bit
uncomfortable with the discrepancy though, and would prefer the -180 to 180
range throughout. I think that that would maximise interoperability.
http://motherlode.ucar.edu:8088/thredds/wcs/testdata/sst.nc?SERVICE=WCS&VERSION=1.0.0&REQUEST=GetCoverage&COVERAGE=tos&CRS=EPSG%3a4326&BBOX=1,-79.5,359,89.5&FORMAT=GeoTIFF&EXCEPTIONS=application/vnd.ogc.se_xml
Regards,
Martin
P.S. "striped.nc" is well named:
http://motherlode.ucar.edu:8088/thredds/wcs/testdata/striped.nc?SERVICEWCS&VERSION=1.0.0&REQUEST=GetCoverage&COVERAGE=ta&Vertical=100.0&CRS=EPSG%3a4326&BBOX=0,-89.4375,358.875,89.4375&FORMAT=GeoTIFF&EXCEPTIONS=application/vnd.ogc.se_xml
