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

Allow to filter style rules based on geometry type for WFS and Vector layers #9185

Open
1 task done
allyoucanmap opened this issue May 19, 2023 · 0 comments
Open
1 task done
Assignees

Comments

@allyoucanmap
Copy link
Contributor

allyoucanmap commented May 19, 2023

Description

The improvements introduced in #9152 include the possibility to apply geometry transformation to polygons and line geometry. When we upload Vector or WFS layer if it's not possible to detect the correct geometry we are applying a default style that includes all base symbolizer (Mark, Line and Fill). In this scenario a LineString geometry will be represented with a the fill outline, line stroke and mark in the middle of the line. We should introduce a way to filter a symbolizer based on the geometry type so we could create a default style that has rules that applies to a specific geometry. A similar approach is used in the sld generic style in GeoServer, maybe we could simplify this by including a $geometry property among the one available in the feature properties (TBD).

What kind of improvement you want to add? (check one with "x", remove the others)

  • Minor changes to existing features

Other useful information

We could consider this issue as part of:

Where additional work of the style editor is needed

@allyoucanmap allyoucanmap changed the title Allow to filter style symbolizer based on geometry type Allow to filter style rules based on geometry type May 19, 2023
@allyoucanmap allyoucanmap changed the title Allow to filter style rules based on geometry type Allow to filter style rules based on geometry type for WFS and Vector layers May 19, 2023
@tdipisa tdipisa added the new label May 19, 2023
@tdipisa tdipisa assigned allyoucanmap and unassigned tdipisa Aug 21, 2023
@tdipisa tdipisa added this to the 2024.01.00 milestone Aug 21, 2023
@tdipisa tdipisa removed the new label Jan 15, 2024
@tdipisa tdipisa modified the milestones: 2024.01.00, 2024.01.01 Feb 27, 2024
@tdipisa tdipisa modified the milestones: 2024.01.01, 2024.01.02 Apr 24, 2024
@tdipisa tdipisa removed this from the 2024.01.02 milestone Jun 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants