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
The cartographic labeling placement mode adds a large offset to labels of MultiPoint geometries when the Distance offset from option is set to From Symbol Bounds. For single-part geometries, the offset does not occur.
In the screenshot below, compare the expected behavior that occurs with the labeling of Point 2 with the undesired behavior that occurs for the features Point 1 and Point 3.
Steps to reproduce the issue
Add a MultiPoint vector layer with multi-part geometries to a new QGIS project
Turn on labeling
By default, cartographic labeling should already be selected
Make sure that the Distance offset from option is set to From Symbol Bounds
I briefly looked at the code, the obstacle geometry is calculated on the bbox of the geometry collection on purpose, see QgsVectorLayerLabelProvider::getPointObstacleGeometry which sets the symbol size, which is then used for the offset in FeaturePart::createCandidatesAtOrderedPositionsOverPoint the single point symbol size is not available at that point so I'm not really sure what should be done here.
@nyalldawson this looks like a bug to me, what do you think?
elpaso
added a commit
to elpaso/QGIS
that referenced
this issue
Jun 8, 2023
What is the bug or the crash?
The cartographic labeling placement mode adds a large offset to labels of MultiPoint geometries when the Distance offset from option is set to
From Symbol Bounds
. For single-part geometries, the offset does not occur.In the screenshot below, compare the expected behavior that occurs with the labeling of Point 2 with the undesired behavior that occurs for the features Point 1 and Point 3.
Steps to reproduce the issue
From Symbol Bounds
Test data set from the screenshot:
multipoint.zip
Versions
Supported QGIS version
New profile
Additional context
No response
The text was updated successfully, but these errors were encountered: