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
Author Name: robert kalasek (@rkalasek)
Original Redmine Issue: 7842
Affected QGIS version: 1.8.0
Redmine category:symbology
i am using a shp and a joined dbf-table with some demographic data
style: graduated
Column: a real 19/11 field from the joined dbf-table
value range of the data: 0.000 - 646.4222
classification of that column results in a wrong set of class braekes (see bug descriptin of "Bug #16723")
lower value of the classification starts at 5.000 instead of 0.000
my personal workaround: adding a class from 0.000 to 5.000
sorting of the resulting classification by clicking into "Range" returns an incorrect result ... see attached image
Please try QGIS master, it should work fine... except for #16725
works fine in qgis master ...
my problem is that i have to do a lecture for students with 1.8. ... since that version is installt in our computer labratory
thx for the information anyway
and 1.9 looks really fine !!!
works fine in qgis master ...
my problem is that i have to do a lecture for students with 1.8. ... since that version is installt in our computer labratory
you can show both the bug and also the fix, and so show that qgis is a quite dynamic project :)
cheers!
status_id was changed from Feedback to Closed
resolution was changed from to worksforme
qgib
added
Bug
Either a bug report, or a bug fix. Let's hope for the latter!
Symbology
Related to vector layer symbology or renderers
labels
May 24, 2019
Author Name: robert kalasek (@rkalasek)
Original Redmine Issue: 7842
Affected QGIS version: 1.8.0
Redmine category:symbology
i am using a shp and a joined dbf-table with some demographic data
style: graduated
Column: a real 19/11 field from the joined dbf-table
value range of the data: 0.000 - 646.4222
classification of that column results in a wrong set of class braekes (see bug descriptin of "Bug #16723")
lower value of the classification starts at 5.000 instead of 0.000
my personal workaround: adding a class from 0.000 to 5.000
sorting of the resulting classification by clicking into "Range" returns an incorrect result ... see attached image
The text was updated successfully, but these errors were encountered: