Bug report #21046
Updated by Jürgen Fischer almost 6 years ago
Related to Continuation of #21045
This WCS:
http://thredds.ucar.edu/thredds/wcs/grib/NCEP/WW3/Regional_US_West_Coast/Best
If I try and add a layer from this WCS, QGIS makes a bad request and the server response is this exception:
<pre>
<?xml version="1.0" encoding="UTF-8"?>
<ServiceExceptionReport xmlns="http://www.opengis.net/ogc" version="1.2.0">
<ServiceException code="InvalidParameterValue" locator="CRS">Request CRS [EPSG:0 [Latitude_Longitude]] not allowed [OGC:CRS84].</ServiceException>
</ServiceExceptionReport>
</pre>
Except what QGIS reports is this:
<pre>
Invalid Layer : WCS provider Cannot get test dataset.
Raster layer Provider is not valid (provider: wcs, URI: cache=PreferNetwork&crs&dpiMode=7&format=GeoTIFF_Float&identifier=Wind_speed_surface&time=2018-12-21T00:00:00Z&url=http://thredds.ucar.edu/thredds/wcs/grib/NCEP/WW3/Regional_US_West_Coast/Best
</pre>
So the WCS handler doesn't seem to be correctly handling exceptions - it's passing them straight to the "Raster layer Provider" which of course barfs. Instead, the WCS error should be parsed and exposed to the user.
This WCS:
http://thredds.ucar.edu/thredds/wcs/grib/NCEP/WW3/Regional_US_West_Coast/Best
If I try and add a layer from this WCS, QGIS makes a bad request and the server response is this exception:
<pre>
<?xml version="1.0" encoding="UTF-8"?>
<ServiceExceptionReport xmlns="http://www.opengis.net/ogc" version="1.2.0">
<ServiceException code="InvalidParameterValue" locator="CRS">Request CRS [EPSG:0 [Latitude_Longitude]] not allowed [OGC:CRS84].</ServiceException>
</ServiceExceptionReport>
</pre>
Except what QGIS reports is this:
<pre>
Invalid Layer : WCS provider Cannot get test dataset.
Raster layer Provider is not valid (provider: wcs, URI: cache=PreferNetwork&crs&dpiMode=7&format=GeoTIFF_Float&identifier=Wind_speed_surface&time=2018-12-21T00:00:00Z&url=http://thredds.ucar.edu/thredds/wcs/grib/NCEP/WW3/Regional_US_West_Coast/Best
</pre>
So the WCS handler doesn't seem to be correctly handling exceptions - it's passing them straight to the "Raster layer Provider" which of course barfs. Instead, the WCS error should be parsed and exposed to the user.