-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Missing labels with the new labeling system #12872
Comments
Author Name: Jean-Roc Morreale (@Jean-Roc) The bug is due to topological errors in the polygons, the labels appears when it is corrected (not self-intersection). This behavior is making the use of the new label engine harder on gps data collected with centimetric gps, if the surveyor makes a small wrong move then the data has to be manually corrected to be labeled (automatic cleaning does not give good result). The old labelling engine works on both uncorrected an corrected data. |
Author Name: Giovanni Manghi (@gioman)
|
Author Name: michele zanolli (michele zanolli) Maybe this problem is related to the following: I am having problems with curved labeling with my layer of lines (see attached shapefile). Enable the advanced option "Show all labels (i.e. including colliding labels")
|
Author Name: Giovanni Manghi (@gioman) michele zanolli wrote:
Hi Michele, this missing curved labels should be another issue, please file a separate ticket.
|
Author Name: Paolo Cavallini (@pcav)
|
Author Name: Paolo Cavallini (@pcav)
|
Author Name: Martin Dobias (@wonder-sk)
|
Author Name: Nathan Woodrow (@NathanW2) These are all implemented in 2.0 >
|
Author Name: Jean-Roc Morreale (@Jean-Roc)
Original Redmine Issue: 2812
Affected QGIS version: master
Redmine category:vectors
Hi,
The new labeling system doesn't display all the labels of a layer, see the joined file for an example using an integer field for labels. The parameters used are free placement and no obstacles, activating colliding and candidate labels modify nothing.
The old labeling system displays them all, I can reproduce this problem with other layers.
The text was updated successfully, but these errors were encountered: