[Geoserver-users] GeoServer cascading WMS, FeatureInfo is lost

Hey GeoServer users,

I’ve been stuck on this problem for a few days now, so I’m hoping I can find some help here.

I’m currently running GeoServer 2.3 on Ubuntu 12.04 LTS and I’m trying to cascade a WMS service (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 empty response from GeoServer.

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.

According to the documentation is GetFeatureInfo cascading supported for servers that support the application/vnd.ogc.gml feature info format. The server does support this format, so theoretically FeatureInfo cascading shouldn’t be a problem.

After some Wireshark analyzing I’ve found out that GeoServer actually sends out an application/vnd.ogc.gml FeatureInfo request to the cascaded server and gets an actual application/vnd.ogc.gml response (with correct information) back.
I’ve put the request and response on Pastebin: http://pastebin.com/PEiU9kaE

I’m not sure what the problem could be now, because GeoServer does get the correct information sent back, it just doesn’t show any of that information in it’s FeatureInfo responses.

Any ideas?

Kind regards,

Robin K.

On Tue, Apr 9, 2013 at 3:15 PM, Robin Kossi <robinkossi@anonymised.com> wrote:

After some Wireshark analyzing I've found out that GeoServer actually
sends out an application/vnd.ogc.gml FeatureInfo request to the cascaded
server and gets an actual application/vnd.ogc.gml response (with correct
information) back.
I've put the request and response on Pastebin:
http://pastebin.com/PEiU9kaE

The issue here is that the response 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.

Cheers
Andrea

--

GeoServer training in Milan, 6th & 7th June 2013! Visit
http://geoserver.geo-solutions.it for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------