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
The rule-based rendering symbology does not include all the possible general renderers, it lacks :
for point, clustering, heat-map, displacement
for line, merged features
for polygon, inverted, merged features
QGIS already allows to use general symbology representations such as categorized and graduated in the Refine Selected Rules menu for a point layer.
This limits simple use cases such as having cluster points above a render scale and individual point below that scale.
The workarounds exists but are not equivalent :
using the wanted top renderer (for ex. cluster) then selecting in the Renderer menu the rule-based one
it does not allow to change the top renderer setting according to rules (the cluster symbol visibility, its appearance, its distance) as opposed to the categorized and graduated renderers.
duplicating the whole layer, use the point clustering symbology and a render scale
it expands the layer number in the legend, masking it in the project's properties forbids the user to control the visibility
using expressions for most
big learning step for an user
I have not found gh tickets on this subject but a few on stackexchange (1, 2).
Regards,
Jean-Roc
Additional context
No response
The text was updated successfully, but these errors were encountered:
Feature description
Hi,
The rule-based rendering symbology does not include all the possible general renderers, it lacks :
QGIS already allows to use general symbology representations such as categorized and graduated in the Refine Selected Rules menu for a point layer.
This limits simple use cases such as having cluster points above a render scale and individual point below that scale.
The workarounds exists but are not equivalent :
I have not found gh tickets on this subject but a few on stackexchange (1, 2).
Regards,
Jean-Roc
Additional context
No response
The text was updated successfully, but these errors were encountered: