Opened 13 years ago
Last modified 13 years ago
#3330 new bug
Bug: Glitches in Pretty Breaks graduated rendering
Reported by: | Alister | Owned by: | nobody |
---|---|---|---|
Priority: | major: does not work as expected | Milestone: | Version 1.7.0 |
Component: | Symbology | Version: | Trunk |
Keywords: | Cc: | ||
Must Fix for Release: | No | Platform: | Windows |
Platform Version: | XP | Awaiting user input: | no |
Description
Sometimes using "Pretty Breaks" mode the graduated renderer creates unnecessary categories which are larger than the maximum value in the data. The biggest category still has the maximum value as its upper limit.
e.g. in the screenshot attached where the ZN column is used, the maximum value in the data is 1.58
in the screenshot where the CU column is used, the maximum value in the data is 0.145
Because so many extra columns are created in the CU example the effect on the map is much worse, as all the data ends up in a narrow slice of the colour ramp (all the data is be yellow).
I've joined most of the attribute data to some made up shapes and attached it for an example (a few of the shapes got deleted when using the "join attributes" tool for some reason, but it still has the same problems when using "Pretty Breaks").
Attachments (3)
Change History (4)
by , 13 years ago
Attachment: | pretty breaks.PNG added |
---|
by , 13 years ago
Attachment: | pretty breaks1.PNG added |
---|
by , 13 years ago
Attachment: | test_temporal_data.zip added |
---|
Sorry, that explanation might not be clear enough. See the attached screenshots.