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
Categorized layers not rendered at all #22736
Comments
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Norwin Roosen (Norwin Roosen) This still happens in 2.18.16. I can confirm that this only occurs with float values with more than 2 decimals. I am not familiar with the codebase, but this toString() might be the cause: |
Author Name: Giovanni Manghi (@gioman)
can you try test/propose a patch?
This is probably due to the very high (much higher than we should use!) float precision of the shapefile field, but I'd still consider that a regression since it works very well in 2.12. to Some vector layer styles we use stopped rendering at all in 2.14. We usually generate them in Python, but the bug can be reproduced in the UI :
This is probably due to the very high (much higher than we should use!) float precision of the shapefile field, but I'd still consider that a regression since it works very well in 2.12. |
Author Name: Giovanni Manghi (@gioman) End of life notice: QGIS 2.18 LTR Source: QGIS 3.4 has recently become our new Long Term Release (LTR) version. This is a major step in our history – a long term release version based on the massive updates, library upgrades and improvements that we carried out in the course of the 2.x to 3x upgrade cycle. We strongly encourage all users who are currently using QGIS 2.18 LTR as their preferred QGIS release to migrate to QGIS 3.4. This new LTR version will receive regular bugfixes for at least one year. It also includes hundreds of new functions, usability improvements, bugfixes, and other goodies. See the relevant changelogs for a good sampling of all the new features that have gone into version 3.4 Most plugins have been either migrated or incorporated into the core QGIS code base. We strongly discourage the continued use of QGIS 2.18 LTR as it is now officially unsupported, which means we’ll not provide any bug fix releases for it. You should also note that we intend to close all bug tickets referring to the now obsolete LTR version. Original reporters will receive a notification of the ticket closure and are encouraged to check whether the issue persists in the new LTR, in which case they should reopen the ticket. If you would like to better understand the QGIS release roadmap, check out our roadmap page! It outlines the schedule for upcoming releases and will help you plan your deployment of QGIS into an operational environment. The development of QGIS 3.4 LTR has been made possible by the work of hundreds of volunteers, by the investments of companies, professionals, and administrations, and by continuous donations and financial support from many of you. We sincerely thank you all and encourage you to collaborate and support the project even more, for the long term improvement and sustainability of the QGIS project.
|
Author Name: François-Xavier Thomas (François-Xavier Thomas)
Original Redmine Issue: 14779
Affected QGIS version: 2.18.16
Redmine category:vectors
Some vector layer styles we use stopped rendering at all in 2.14. We usually generate them in Python, but the bug can be reproduced in the UI :
This is probably due to the very high (much higher than we should use!) float precision of the shapefile field, but I'd still consider that a regression since it works very well in 2.12.
The text was updated successfully, but these errors were encountered: