offered_crs is not defined

Question

offered_crs is not defined

Closed this issue 7 years ago · 11 comments

When I connect to Rasdaman sample database and click GetCoverage for AverageChloro I get the error
NameError: global name 'offered_crs' is not defined (qgswcsclient2dialog.py 103 in new_function)

howff commented 7 years ago

gc.txt

Answer 1 · 2017-11-16T17:48:22.000Z

Hi hwoff,
could you please provide me with some more information.
which Qgis version; which OS, are you using. Furthermore:
Start Qgis new. Then, in Qgis please start the python shell --> Menu-Plugins-Python Console; then start the WCSClient2 Plugin and run the above operations.
Please send me the output from the console so I get some idea what is going on.
regards
Christian

Answer 2 · 2017-11-16T17:56:08.000Z

That was the output from the console

Answer 3 · 2017-11-17T12:43:45.000Z

It looks like you forgot to paste the output ?

Answer 4 · 2017-11-17T12:46:38.000Z

? It's in the original issue report!

Answer 5 · 2017-11-17T13:21:47.000Z

I mean the full output, not just the last line.

Answer 6 · 2017-11-17T14:05:43.000Z

I tried it another six times and that is all I get. Nothing else.

Answer 7 · 2017-11-17T14:13:46.000Z

A typical output in the QGis Python Console would look like this:
Python Console
Use iface to access QGIS API interface or Type help(iface) for more info
You choose: OGC: WCS 2.0/EO-WCS 1.0 - Reference Implemetation (EOxServer) URL: http://ows.eox.at/cite/eoxserver/ows?
WCS-Version: 2.0.1
REQUEST: http://ows.eox.at/cite/eoxserver/ows?service=WCS&request=GetCapabilities&sections=All
Selected Item: MERIS_MGVI 2006-07-01T00:00:00Z 2010-09-30T23:59:59.990000Z 90.000000 180.000000 -90.000000 -180.000000 S
Selected EO-Series: ['MERIS_MGVI']
REQUEST: http://ows.eox.at/cite/eoxserver/ows?service=WCS&version=2.0.1&request=DescribeEOCoverageSet&eoID=MERIS_MGVI&containment=overlaps&count=10
Selected CoverageID: ['L3_ENV_MER_MGVI_m__20070801_GLOB_SI_ESA']
REQUEST: http://ows.eox.at/cite/eoxserver/ows?service=WCS&version=2.0.1&request=GetCoverage&coverageid=L3_ENV_MER_MGVI_m__20070801_GLOB_SI_ESA&format=image/tiff&outputcrs=http://www.opengis.net/def/crs/EPSG/0/4326&interpolation=average

... and then somewhere would come the traceback for the error

Answer 8 · 2017-11-17T16:12:17.000Z

You choose: rasdaman URL: http://localhost:8080/rasdaman/ows/wcs2?
WCS-Version: 2.0.1
REQUEST: http://localhost:8080/rasdaman/ows/wcs2?service=WCS&request=GetCapabilities
Selected Item: 2017_11_15 C
Selected CoverageID: ['2017_11_15']
Then the error message is in the Python error window.

I have to admit I don't always get this error any more, sometimes I get other errors but I'll report them separately. (I've never successfully got anything at all to work, yet!) .

Answer 9 · 2017-11-20T09:33:19.000Z

Hey,
could you please also post the output of the http://localhost:8080/rasdaman/ows/wcs2?service=WCS&request=GetCapabilities request.

Answer 10 · 2017-11-23T10:24:58.000Z

Hi howff,
I had a look at your GetCapabilities.xml. The section for the CRS is missing.
I.e. something along these lines should be there.
wcs:Extension
crs:CrsMetadata
crs:crsSupportedhttp://www.opengis.net/def/crs/EPSG/0/4326</crs:crsSupported>
crs:crsSupportedhttp://www.opengis.net/def/crs/EPSG/0/3857</crs:crsSupported>
crs:crsSupportedhttp://www.opengis.net/def/crs/EPSG/0/3035</crs:crsSupported>
</crs:CrsMetadata>
...

However, the QgsWcsClient2 has a fallback included for such a cases, i.e. the 'offered_crs' it will be set to EPSG:4326 for cases where nor crs are provided. So I assume that there are also some other issues with the rasdaman installation (which is know to be very tricky).
Unfortunately I can't do much if I don't get at least the traceback messages providing a more detailed description and allowing the analysis of the error.