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: Per Gammerath (Per Gammerath)
Original Redmine Issue: 9601
Affected QGIS version: master
Redmine category:symbology
Point symbols can be angled through Data Defined Properties, but this function does not work with Point Displacement. Only point symbols that have not been displaced, are angled as prescribed. The Size property works though.
Is this a bug? And when can this be fixed?
I can confirm the issue also for the size. It seems that for both the rotation and size the value used is the one of the first feature of the cluster, that is applied to all others.
PS
about "when": it depends, if it critical for you to have it fixed soon better have a look to the qgis page where are listed the companies that offer commercial support.
subject was changed from Point displacement angles to Point displacement: data defined size and angle does not work
Thank you for acknowledging the issue. I hope that it can be fixed in the next version. Actually, I would also hope to see some more options in the Displacement panel. Fx an option to add a leader from the origin to the displaced point, like in Google earth.
Fixed in changeset "a6f96ba51b736cc97b3d8d6a848940737a46a6bc".
status_id was changed from Open to Closed
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: Per Gammerath (Per Gammerath)
Original Redmine Issue: 9601
Affected QGIS version: master
Redmine category:symbology
Point symbols can be angled through Data Defined Properties, but this function does not work with Point Displacement. Only point symbols that have not been displaced, are angled as prescribed. The Size property works though.
Is this a bug? And when can this be fixed?
The text was updated successfully, but these errors were encountered: