[mapserver-users] RE Cascaded WMS GetFeatureInfo

[Rahkonen Jukka (MML)]

Hi,

I have never tried to cascade GetFeatureInfo from Mapserver to other WMS servers but I have tried to do that when Geoserver is used for cascading our Mapserver. I would say that it is complicated.  First issue is that the list of supported info_formats is a per service feature, not per layer. For example Geoserver by default supports these formats:

<GetFeatureInfo>
<Format>text/plain</Format>
<Format>application/vnd.ogc.gml</Format>
<Format>application/vnd.ogc.gml/3.1.1</Format>
<Format>text/html</Format>
<Format>text/javascript</Format>
<Format>application/json</Format>

If I try to cascade Mapserver WMS that is configured to support only info_format=text/html with Geoserver, then users can't know that info_format=text/plain can't work with the cascaded layer. Actually no info_format will work in this theoretical case because Geoserve is always using "application/vnd.ogc.gml" when it cascades GetFeatureInfo but our Mapserver was  not configured to support that.

I have no idea about how Mapserver should be configured to support GetFeatureInfo for cascaded WMS layers. I do not believe that it is even possible to do it generally in a reliable way so that any WMS could do it successfully with any other WMS. Probably Mapserver can do is in some cases because http://mapserver.org/ogc/wms_client.html documents
*  GetFeatureInfo is not fully supported since the output of getFeatureInfo is left to the discretion of the remote server. A method layer.getWMSFeatureInfoURL() has been added to MapScript for applications that want to access featureInfo results and handle them directly

-Jukka Rahkonen-

Berger, Cora wrote:


Dear Steve,
yes, I have read this. My layers do cascade. The only thing that doesn't work is the GetFeatureInfo Request.
The original WMS supports GetFeatureInfo. But if I connect to this WMS and use it as a layer for my new WMS GetFeatureInfo stops working.
Cora



Von: Steve.Toutant at inspq.qc.ca<mailto:Steve.Toutant at inspq.qc.ca> [mailto:Steve.Toutant at inspq.qc.ca]
Gesendet: Mittwoch, 28. Oktober 2015 13:25
An: Berger, Cora
Cc: 'mapserver-users at lists.osgeo.org'; mapserver-users
Betreff: RE [mapserver-users] Cascaded WMS GetFeatureInfo

Cora have you read this?
http://mapserver.org/ogc/wms_server.html#cascading-wms-request
It might help to know why a layer is not cascaded

What happen if you don't modify the style?
steve




"Berger, Cora" <cora.berger at bezreg-koeln.nrw.de<mailto:cora.berger at bezreg-koeln.nrw.de>>@lists.osgeo.org
Envoyé par : "mapserver-users" <mapserver-users-bounces at lists.osgeo.org<mailto:mapserver-users-bounces at lists.osgeo.org>>

2015-10-27 04:01

A

"'mapserver-users at lists.osgeo.org'" <mapserver-users at lists.osgeo.org<mailto:mapserver-users at lists.osgeo.org>>

cc

Objet

[mapserver-users] Cascaded WMS GetFeatureInfo









Hello everybody,
I am building a cascaded WMS. My layers all have connectiontype WMS and all of them use one layer of the same WMS as source. The only thing I change is the style of the original WMS.
My problem is that the GetFeatureInfo does not cascade. I am using Mapserver 7.0. I read that the GetFeatureInfo request supports cascading. All requests are enabled in the metadata. Do I have to add a special tag in the metatada or layer section to "pass through" the GetFeatureInfo from the original WMS?

Thanks for your help.

Best regards

Cora Berger


_______________________________________________
mapserver-users mailing list
mapserver-users at lists.osgeo.org<mailto:mapserver-users at lists.osgeo.org>
http://lists.osgeo.org/mailman/listinfo/mapserver-users


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-users/attachments/20151029/4e84ebb3/attachment.htm>