Bug report #13558
[Regression] Label/diagram placement on centroid is broken for multipolygons
| Status: | Closed | ||
|---|---|---|---|
| Priority: | Severe/Regression | ||
| Assignee: | - | ||
| Category: | Labelling | ||
| Affected QGIS version: | master | Regression?: | No |
| Operating System: | Easy fix?: | No | |
| Pull Request or Patch supplied: | No | Resolution: | fixed/implemented |
| Crashes QGIS or corrupts data: | No | Copied to github as #: | 21600 |
Description
Label/diagram placement on centroid in master seems to be off compared to 2.10: for multipolygons, it seems to randomly chose the centroid of one part rather than the old behavior which seemed to use the whole multipart feature to compute the centroid.
In the following example the diagram is put on the centroid with high priority and the label settings are shown.
Tested on nightly OSGeo4W
History
#1
Updated by Anita Graser about 9 years ago
- File 210-vs-master.png added
#2
Updated by Nyall Dawson about 9 years ago
- Priority changed from High to Severe/Regression
#3
Updated by Anita Graser about 9 years ago
- Subject changed from [Regression] Label/diagram placement on centroid is broken for multipolgons to [Regression] Label/diagram placement on centroid is broken for multipolygons
#4
Updated by Anita Graser about 9 years ago
- File label-partial-feature.png added
Update info: If label all parts of multipart feature is enabled ...
When the complete multipolygon is visible in the map view, there are no label candidates on the main land. They appear if the feature is moved partially outside the map view:
#5
Updated by Nyall Dawson about 9 years ago
Seems to be caused by the recent GEOS c++ changes (tolerance) - if I build without the geos c++ library set then the placement matches 2.10. Can also confirm that https://github.com/qgis/QGIS/pull/2353 fixes this.
#6
Updated by Nyall Dawson about 9 years ago
- Status changed from Open to Feedback
Can you please re-test with current master? PR 2353 has been merged, which fixed the issue for me.
#7
Updated by Anita Graser about 9 years ago
- Resolution set to fixed/implemented
- Status changed from Feedback to Closed
- Target version changed from Future Release - High Priority to Version 2.12
- % Done changed from 0 to 100
Looks fine today. Thanks!