[Geoserver-devel] [JIRA] (GEOS-7293) GetFeatureInfo on a gruop layer with at least one non-queryable layer fails

GeoServer GeoServer Developer
1

César Díaz created an issue

GeoServer / BugGEOS-7293

GetFeatureInfo on a gruop layer with at least one non-queryable layer fails

Issue Type:

BugBug

Affects Versions:

2.7.2

Assignee:

Unassigned

Components:

WMS

Created:

04/Nov/15 11:12 AM

Environment:

Windows 2008
Geoserver MSI installer with Jetty

Priority:

MediumMedium

Reporter:

César Díaz

On a fresh geoserver install - with Jetty, manual startup.

  • Log in to the web console.
  • Create a group layer.
  • Add a bunch of layers to the recently created group layer.
  • Make sure that at least one of the layers added to the group is non queryable. To ensure so, open the layer, go to the Publishing tab and under the WMS Settings section uncheck the ‘queryable’ checkbox.
  • Finally, send a GetFeatureInfo query using the group layer as the single value for the QUERY_LAYERS parameter. Tested using the OpenLayers map viewer available in the Layer Preview page.

The following in an example of the error produced, being ‘topp:tasmania_state_boundaries’ a non queryable layer inside the group requested:

<?xml version=“1.0” encoding=“UTF-8” standalone=“no”?><!DOCTYPE ServiceExceptionReport SYSTEM “http://pmpwvinet07.tcsa.local:8087/geoserver/schemas/wms/1.1.1/WMS_exception_1_1_1.dtd”> <ServiceExceptionReport version=“1.1.1” > <ServiceException code=“OperationNotSupported” locator=“QUERY_LAYERS”>
Layer topp:tasmania_state_boundaries is not queryable
</ServiceException></ServiceExceptionReport>

The desired behaviour would be having the results related only to queryable layers. That would require Geoserver being able to handle non queryable layers by ignoring them, instead of throwing an error.

Add Comment

Add Comment

This message was sent by Atlassian JIRA (v7.0.0-OD-08-005#70107-sha1:5fb2f7e)

Atlassian logo