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
I'm not sure if this is a bug report or a feature request, but I guess the first.
I like to use a graduated symbology for some vector data.
Let's say my classes are 1-10, 11-20, 21-30, ...
My legend should only show the upper limit for each class.
The option "Legend Format" says I should use "%1" for the lower limit and "%2" for the upper limit.
So I thought when I write "< %2" my legend should be filled with "< 10", "< 20", "< 30", ...
Instead it is filled with "< 1", "< 11", "< 21", ... - the lower limit.
I tried with different data sources (Shape, GPKG, PostGIS) and it also doesn't matter if the attribute is integer or double.
Steps to reproduce the issue
Load any vector data with at least one attribute which contains numbers.
Create a graduated symbology
Change "Legend Format" to something with "%2" (without "%1") and look into the legend
Versions
<style type="text/css">
p, li { white-space: pre-wrap; }
</style>
What is the bug or the crash?
I'm not sure if this is a bug report or a feature request, but I guess the first.
I like to use a graduated symbology for some vector data.
Let's say my classes are 1-10, 11-20, 21-30, ...
My legend should only show the upper limit for each class.
The option "Legend Format" says I should use "%1" for the lower limit and "%2" for the upper limit.
So I thought when I write "< %2" my legend should be filled with "< 10", "< 20", "< 30", ...
Instead it is filled with "< 1", "< 11", "< 21", ... - the lower limit.
I tried with different data sources (Shape, GPKG, PostGIS) and it also doesn't matter if the attribute is integer or double.
Steps to reproduce the issue
Versions
<style type="text/css"> p, li { white-space: pre-wrap; } </style>Supported QGIS version
New profile
Additional context
No response
The text was updated successfully, but these errors were encountered: