Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WMS caps: add queryable attribute for non-leaf layers #5220

Closed
wants to merge 1 commit into from

Conversation

rouault
Copy link
Contributor

@rouault rouault commented Jan 12, 2016

@sdlime @jratike80

Related to discussion
https://lists.osgeo.org/pipermail/mapserver-users/2016-January/078538.html

Currently MapServer only sets the queryable attribute on leaf layers.
This changeset also adds it non-leaf layers of group/layer_group. A layer
is queryable if and only if all of its sublayers are queryable.

Would require adjusting a few msautotest results. Not sure if it is branch-7-0 material or master only. msautotest doesn't seem to include tests with several level of nesting.

Related to discussion
https://lists.osgeo.org/pipermail/mapserver-users/2016-January/078538.html

Currently MapServer only sets the queryable attribute on leaf layers.
This changeset also adds it non-leaf layers of group/layer_group. A layer
is queryable if and only if all of its sublayers are queryable.
@tbonfort
Copy link
Member

FWIW, I think a layer should become queryable if at least one of its sublayers is queryable (the actual query would only return results from the queryable sublayers)

@rouault
Copy link
Contributor Author

rouault commented Jan 12, 2016

@tbonfort My understanding of the discussion was that a layer is currently queryable only if all its sublayers are queryable. But I didn't check the code. Or is your remark about modifying the current behaviour ? Do the WMS specs say something about the expected behaviour ?

@tbonfort
Copy link
Member

@rouault as per https://lists.osgeo.org/pipermail/mapserver-users/2016-January/078541.html it would seem that geoserver does what I would assume to be the default behavior, i.e. layer queryable if at least one sublayer queryable. If that's not easily doable I'm fine with starting with your proposed behavior.

@tbonfort tbonfort added this to the 7.2 Release milestone Feb 24, 2016
@landryb
Copy link
Contributor

landryb commented Oct 14, 2016

Fwiw, i stumbled upon this behaviour, and would welcome the change. If one of the sublayers is queryable, just mark the layer as queryable. Right now i'm grouping a TILEINDEX layer and a regular layer, and since a TILEINDEX layer is forcedly non-queryable (cf mapquery.c#L122) the group layer isnt queryable.. while i'd like queries to be able to return values from the 'regular layer'.

@tigerfoot
Copy link
Contributor

+1

@tbonfort tbonfort mentioned this pull request Jan 17, 2017
6 tasks
@sdlime
Copy link
Member

sdlime commented Aug 23, 2017

@rouault, what do you want to do this one? Seems like a positive change although I see a Travis is failing.

@rouault
Copy link
Contributor Author

rouault commented Dec 20, 2017

Note: this PR shouldn't be merged. From above comments, a better behaviour would be to make a layer queriable as soon as one of its sublayers is also queriable.

@sdlime
Copy link
Member

sdlime commented Mar 20, 2018

@rouault, can I close this?

@rouault
Copy link
Contributor Author

rouault commented Mar 20, 2018

I'm clossing this pull request, because it doesn't implement the desired behaviour, but opened #5570 to track the issue though

@rouault rouault closed this Mar 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants