search

RAMP-PCAR / RAMP-PCAR

Source code for the RAMP-PCAR web mapping platform. See https://github.com/ramp4-pcar4/ramp4-pcar4 for current version
https://ramp-pcar.github.io
5 stars 4 forks source link

GetFeatureInfo is not working with WMS Services for a root layer or a group layer #12

Open davBel opened 9 years ago

davBel commented 9 years ago

When we use the Add Dataset Function with a WMS Service, the GetFeatureInfo is not working for a root layer or a group layer. Sometimes there is a hierarchy in the GetCapablities and the GetFeatureInfo is working only for the leafs. (e.g. for the service http://maps.geogratis.gc.ca/wms/eab_en?service=wms&version=1.3.0&request=GetCapabilities&layers=emerald_ash_borer_reg_area , the GetFeatureInfo doesn't work for the layer=emerald_ash_borer_reg_area and layer=eab)

alyec commented 9 years ago

I think in this case the server is not setting the queryable attribute on emerald_ash_borer_reg_area and eab. When I looked at the GetCapabilities response the two layers you mentioned did not have queryable set on them, but the three leaf nodes did. Do you have any other WMSes which have queryable="1" set on a group layer?

davBel commented 9 years ago

We are using MapServer and is not possible to add the attribute queryable="1" in the getCapabilities for a root layer or a group layer. The getcapabilities info is generated on the fly according to a MapFile. Is it possible to assume that the layer is queryable=1 if the information is missing?

dan-bowerman commented 9 years ago

I have seen MapServer using queryable="1" for root/group layers (see http://geo.weather.gc.ca/geomet/?lang=E&service=WMS&request=GetCapabilities for an example). The getfeatureinfo can also be described in the RCS registration, but as-is, RAMP does not assume queryable=1 when adding a WMS through the RAMP interface. This would need to be treated as a new feature for the viewer if we were to implement this behaviour.