WMS GetFeatureInfo request fails to pickup features classified by sld:ElseFilter in layer's style


1) Create style with SLD containing one rule with some filter and one rule with <sld:ElseFilter /> tag.
2) Assign style to a vector layer (I used PostGIS based) with several features matching provided SLD rules
3) Open layer preview for the layer and click on objects to view their info

Expected result:
Info is displayed for all features of layer both for those correspoding to Filter-Rule and to ElseFilter-rule.

Current result:
Info is not displayed when clicking on features handled by ElseFilter rule in SLD. For features handled by Filter-Rule it works fine.

It seems like WMS GetFeatureInfo request could not get features classified by ElseFilter-rule.




Jukka Rahkonen
December 18, 2017, 7:29 AM

I am not sure if I understand your issue right but it seems that you are mixing the WMS request "GetFeatureInfo" and WFS request "GetFeature". Click on the map is firing the WMS GetFeatureInfo request.

The expected result is that GetFeatureInfo returns info only from those features which show on the map. If feature does not show on the map then no info should be returned either. The reason why the feature is not visible (scale limits, CQL_FILTER, rule in the SLD) should make no difference. Is that your case? If it is, please provide a reproducible way to for making the issue to happen.

Dmitry Ulianov (GrayFox)
December 18, 2017, 7:32 AM

Yep, you are right I mean WMS GetFeatureInfo. WFS is not style-based as I remember. I'll fix the description.
But anyway - features that correspond to ElseFilter-rule are displayed. But clicking on them show no info below map.

Steve Ikeoka
December 18, 2017, 3:35 PM

I had this problem in 2.12.0 but it was fixed in 2.12.1 for me. GetFeatureInfo returns no features if point layer has style that uses sld:ElseFilter

Dmitry Ulianov (GrayFox)
December 18, 2017, 3:41 PM

Hm. Ok. Thanks a lot Steve! I'll check this out tomorrow. Hope this will help and we'll resolve the issue as fixed and dupplicated for the one you've provided

Dmitry Ulianov (GrayFox)
December 19, 2017, 5:13 AM

I've checked. Problem is fixed at 2.12.1 and it is confirmed. I was misinformed about problem appearance at 2.12.
So issue might be closed





Dmitry Ulianov (GrayFox)


Fix versions


Affects versions