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

Vector data - Graduated Symbology - Legend Format - Only use upper limit #51691

Closed
2 tasks done
fmeier1995 opened this issue Feb 1, 2023 · 0 comments · Fixed by #51692
Closed
2 tasks done

Vector data - Graduated Symbology - Legend Format - Only use upper limit #51691

fmeier1995 opened this issue Feb 1, 2023 · 0 comments · Fixed by #51692
Assignees
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter!

Comments

@fmeier1995
Copy link

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.

grafik

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

  1. Load any vector data with at least one attribute which contains numbers.
  2. Create a graduated symbology
  3. 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>
QGIS-Version 3.22.15-Białowieża QGIS-Codeversion ef17ad1
Qt-Version 5.15.3
Python-Version 3.9.5
GDAL-Version 3.6.2
PROJ-Version 9.1.1
EPSG-Registraturdatenbankversion v10.076 (2022-08-31)
GEOS-Version 3.11.1-CAPI-1.17.1
SQLite-Version 3.39.4
PDAL-Version 2.4.3
PostgreSQL-Client-Version 14.3
SpatiaLite-Version 5.0.1
QWT-Version 6.1.6
QScintilla2-Version 2.13.1
BS-Version Windows 10 Version 2009
       
Aktive Python-Erweiterungen
db_manager 0.1.20
grassprovider 2.12.99
MetaSearch 0.3.5
processing 2.12.99
sagaprovider 2.12.99
GeoCoding 2.18
quick_map_services 0.19.32
SpreadsheetLayers 2.0.1
QPackage 1.5
DissolveWithStats 0.6
qchainage 3.0.1
autoSaver 2.6

Supported QGIS version

  • I'm running a supported QGIS version according to the roadmap.

New profile

  • I tried with a new QGIS profile

Additional context

No response

@fmeier1995 fmeier1995 added the Bug Either a bug report, or a bug fix. Let's hope for the latter! label Feb 1, 2023
@elpaso elpaso self-assigned this Feb 1, 2023
elpaso added a commit to elpaso/QGIS that referenced this issue Feb 1, 2023
troopa81 pushed a commit that referenced this issue Feb 1, 2023
qgis-bot pushed a commit that referenced this issue Feb 1, 2023
nyalldawson pushed a commit that referenced this issue Feb 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter!
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants