-
Notifications
You must be signed in to change notification settings - Fork 86
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
Support layer group filtering #5250
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fa7934d
to
6eaa347
Compare
6eaa347
to
e7d8a88
Compare
The patch on MapServer has been merge. Please, write a comment here once the GMF demo server has its MapServer version up-to-date. |
e7d8a88
to
712c74f
Compare
Any reason why we don't have the geom filter? |
When we click on get data we should only have the features from the layer Hotel (trigged with the GetData metadata...) |
Here's a snippet from the JSON returned by the themes service:
To my understanding, the label layer returns features because it is queryable. If that's an issue, then it should be logged as a separate task in JIRA, as it is not related to this PR. |
That's an issue intruduced in this PR. I'll look into it. |
The issue has been fixed. Ready for review. |
|
Confirmed, thanks :-) |
The main goal of this patch is to introduce the support of filtering a WMS layer that uses a group as layer name.
To accomplish this, the following change was made.
The creation of attributes within an OGC data source object is made by first checking if there are attributes set for the layers used by the data source in the inner
ogcLayers_
property. Then, they are combined together, i.e. only the attributes that are commonly shared in all layers are kept.From there, the rest works as usual.
Known issue
There is an issue with this approach. To resume: it is currently not supported by MapServer to give the name of the group in the LAYERS parameter while giving only one filter in the FILTER property. Therefore, this patch breaks the MapServer WMS layers in those cases.More about this issue in GSGMF-1133.The above issue has been fixed in MapServer: MapServer/MapServer@ba27152