You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Technically WFS could follow the same workflow of WMS in relation to filtering even if it’s not the optimal solution in terms of performance and request. It would be better to filter directly content already downloaded but this means a review of the current workflow so we could think just these additional tasks:
Convert the WFS style filter in CQL to be applied to the request
editing of the selected style and changing the rule with the visual style editor (internal editing): the behavior should be the same as reported in #10684: Legend filtering for GeoServer WMS layers #10718 (comment) and so a warning should appear when the user comes back to the TOC after having changed the style
This is a summary of the expected implementation steps:
1- For the UI part:
handle adding checkbox in catalog and layer settings in TOC for enabling/disabling interactive legend [the part in layer settings in TOC --> common with Vector]
handle the same behaviour in WMS of hovering effect on the TOC legend items if they present a filter and implement the select effect as well [Add interactivity to the Vector Legend] --> common with Vector
2- For the logic:
Now user can create a style includes rules [classification for example] which is on geostyler format
in general for WFS filter layer, it is using cql filter expression to filter the layer into the server sending the CQL
It will need a converter from geostyler [which comes from classification style for example] to cql that will be needed when user clicks on legend item to implement filter process
change in style/disable interactive legend from layer settings will reset the filter like WMS
Other useful information
The text was updated successfully, but these errors were encountered:
…art]
Description:
- handle the functionality of interactive legend for WFS layers
- create geostyler converter to cql
- handle saving the legend filter of layer into layerFilter object in saving
- handle showing incompatible message in case change into filtered style
- add unit tests
- add translations
Description
Technically WFS could follow the same workflow of WMS in relation to filtering even if it’s not the optimal solution in terms of performance and request. It would be better to filter directly content already downloaded but this means a review of the current workflow so we could think just these additional tasks:
This is a summary of the expected implementation steps:
1- For the UI part:
2- For the logic:
Other useful information
The text was updated successfully, but these errors were encountered: