-
Notifications
You must be signed in to change notification settings - Fork 410
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
Interactive legend for TOC layers [WFS Layer part] #10736
Comments
12 tasks
mahmoudadel54
added a commit
to mahmoudadel54/MapStore2
that referenced
this issue
Jan 13, 2025
…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
12 tasks
12 tasks
mahmoudadel54
added a commit
to mahmoudadel54/MapStore2
that referenced
this issue
Jan 13, 2025
mahmoudadel54
added a commit
to mahmoudadel54/MapStore2
that referenced
this issue
Jan 17, 2025
…art] (resolve reviews) - fix issue of activating interactive legend even if experimentalInteractiveLegend = false in localConfig - remove serverType check for wfs interactivity legend display - replace owner prop with interactive prop for wms and wfs - handle not calling legend filter handler in case not activate the interactivity or no rule to apply - add double check for geostyler if it is a direct array or has body in converter file - reset miscSettings in CommonAdvancedSettings test file in afterEach - add tranlations
mahmoudadel54
added a commit
to mahmoudadel54/MapStore2
that referenced
this issue
Jan 17, 2025
mahmoudadel54
added a commit
to mahmoudadel54/MapStore2
that referenced
this issue
Jan 17, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: