Take the 2-minute tour ×
Geographic Information Systems Stack Exchange is a question and answer site for cartographers, geographers and GIS professionals. It's 100% free, no registration required.

I'm trying to cascade a WMS service in GeoServer (http://grb.agiv.be/geodiensten/raadpleegdiensten/GRB/wms?REQUEST=GetCapabilities&SERVICE=WMS).

I can view the cascaded layers just fine, but whenever I try to get FeatureInfo from a cascaded layer I get an error message saying that the layer isn't queryable.

I can get the FeatureInfo from the original service, so I know that there is actual FeatureInfo on the original layers.

I've combed through every available WMS setting in GeoServer but only found the 'Queryable' option in the 'WMS Settings' panel in the Publishing tab of the cascaded layers, which is obviously enabled.

Is there anything I'm missing, or is it just not possible to get FeatureInfo from a cascaded WMS service?

share|improve this question
add comment

2 Answers

According to the documentation:

GetFeatureInfo cascading for servers that do support the application/vnd.ogc.gml feature info format. Works in both standard and reprojected case.

It seems that your server does provide that format but I haven't actually tested that it does. You may need to make sure that your request is also in that format?

So the bottom line is that it should be working - can you check what the request that is sent to the remote server looks like (may be with wireshark if you don't have access to the remote logs).

share|improve this answer
    
GeoServer actually sends the FeatureInfo request to the WMS server and also gets a GML response which contains correct information, I put the request and response in a Pastebin file: pastebin.com/PEiU9kaE I don't understand why GeoServer gets an actual vnd.ogc.gml response with information, but still says the layer isn't queryable... –  Robin_K Apr 9 '13 at 9:52
    
what format did you ask for in your request? –  iant Apr 9 '13 at 9:53
    
The format asked is also application/vnd.ogc.gml –  Robin_K Apr 9 '13 at 9:55
    
I actually just realized that I don't get the 'not queryable' error, I just get an empty response from GeoServer in Gaia: 'no features were found'. With the internal OpenLayers preview I get the 'loading, please wait' message for a few seconds, also with no results. When I check the nodelist div which should contain the feature info I just see a title and some inline table css, but also no actual information –  Robin_K Apr 9 '13 at 9:59
add comment
up vote 0 down vote accepted

After some more digging around I contacted the GeoServer-users mailinglist, and got an answer:

The problem is tied to the response of the server I'm trying to cascade.

The GML response from the WMS server is not a standard feature collection but some weird msGMLOutput construct that would need a custom parser.

To interpret it, real GML seems to start only at the third nested element. So, this would need someone writing such parser.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.