WMS not working in QGIS about gsky HOT 4 CLOSED

Current version of GSKY can serve legends using the request=GetLegendGraphic url parameter. I've checked current WMS specs and it does not list GetLegendGraphic nor GetLeg as standard functionality.

I think Geoserver implements request=GetLegendGraphic for publishing color scales and legends, which is what TerriaJS consumes, but I think it's their own standard.

Solving this issue could be as simple as adding GetLeg as an alternative name for the legends functionality in the WMS switch clause at ows.go.

@kdruken Could you do some research to find out if the legend output format for GetLeg is the same as Geoserver's GetLegendGraphic? Also, is this error caused using QGis native WMS functionalities or is it using a third party plugin?

from gsky.

This appears to be related to issue #15 that I raised, whereby the GetCaps document advertises URLs to legend graphics that don't exist. QGIS looks in the GetCaps document to obtain the legend graphic URL when loading the WMS layer, and is failing on the ones provided with this service because they don't exist.

I'm pretty sure that "GetLeg" above is just "GetLegendGraphic" in the QGIS error message being cutoff, i.e. I don't think QGIS is issuing a "GetLeg" request.

Note that the GetLegendGraphic operation is part of the OGC "Styled Layer Descriptor profile of the Web Map Service Implementation Specification".

from gsky.

@prl900 - apologies, sorry for confusion and not being more clear. Believe that it's just cutoff and is the GetLegend as @asedgmen says above.

Had a feeling it was probably related to one of those OGC issues- thanks @asedgmen!

from gsky.

I had the same issue today (I think):
QGis V3.0.3.

from gsky.