-
-
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
curved labels: only a few are drawn #12173
Comments
Author Name: Martin Dobias (@wonder-sk) The problem is that either the shapes are too short (the label wouldn't fit on the line) or the shapes are too complex and creation of labels candidates fails because the succesive characters would be otherwise rotated "too much", resulting in unreadable labels. I don't know what should be a correct solution for this. The engine could try to detect such complex shapes and try to simplify on-the-fly them before creating candidates... |
Author Name: Borys Jurgiel (@borysiasty) Even on simpler lines, as streets, the curvature threshold seems too low. I can imagine much more curved labels would be still good-looking. Anyway, even if it's acceptable on display, on printouts (or exported files; no matter rasterized or not) it is definitely not. See screenshots label2-* (also wrong scaling and #12856 are visible). |
Author Name: Alister Hood (@AlisterH) (sorry, I was meant to post this before attaching) I agree with this:
But I also think that this is necessary:
See the labelling on the roads in P1080123_cropped_1.jpg for an example. |
Author Name: Paolo Cavallini (@pcav)
|
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Paolo Cavallini (@pcav)
|
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Paolo Cavallini (@pcav)
|
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Anita Graser (@anitagraser)
|
Author Name: Larry Shaffer (Larry Shaffer) See #15916 (comment) for update on related issue. Please test with ee12df2 and inside and outside angles greater than 20 to see higher label count (especially if you still have the original data). Some comparison screen snaps again would be nice. Any settings higher than inside of 30 or outside of 50 (and possibly lower in some cases) will start producing some funky-looking labels. QGIS <= 1.8 had a setting of 20 for both angles.
|
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Paolo Cavallini (@pcav)
|
Author Name: Paolo Cavallini (@pcav) Still far from optimal |
Author Name: aperi2007 - (aperi2007 -) Hi, It is quite flexible because it give the grant to not lost any label. Actually no one of out power users use the curve string solution. Because they are always the question to know if lost any label. I guess the parallel string as an otherwise solution could be supported using a checkbox to active it optionally. I like to know if this feature could be accepted. Please note that don't mean that we are capble to fund this solution. One time to decide what is the solution. Regards, Andrea. |
Author Name: Paolo Cavallini (@pcav) As discussed on the mailing list long ago, probably the best approach would be to simplify (generalize) complex (multi)lines on the fly, so that the labels will follow the best approximation to the original curve, without becoming too garbled or disappearing altogether. |
Author Name: aperi2007 - (aperi2007 -) The simplify approach is could be affordable for a print goal . Almost if the question is a run-time simplify approach. Are you speaking of an extra layer maually added to the project and simplified previously offline. I guess the primary question is not resolved however. Or you are speaking of an iterative simplification increasing the simplify untile the label could appear ? This could work but I guess it could be mortally slow. It could slow the map production of an impredictable time due to the situation of label on that portion f map. A. |
Author Name: Paolo Cavallini (@pcav) I suggest the same approach as Alvaro OTF simplification, which is actually quite fast. |
Author Name: aperi2007 - (aperi2007 -) Hi, we like to understand if this problem is resolvable or not. The solution proposed:
I guess in not a sure solution. The try to introduce this need n a simplifiy algorithm will introduce an iterative procedure that could put the time to elaborate to infinite. I guess to grant this is necessary to introduce a rule specific like this: |
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Paolo Cavallini (@pcav) Still true in master. |
Author Name: Paolo Cavallini (@pcav)
|
Author Name: Tom Grundy (Tom Grundy) This problem still exists in 3.2.1. I tried increasing letter spacing and changing to all-caps for the letter sizes to be more predictable, but did not see any improvement. Images attached with labeling set to parallel and another with labeling set to curved with no other changes.
|
Author Name: Giovanni Manghi (@gioman)
|
conjunction with the "merge connected lines" setting Refs qgis#12173
with line networks that contains forks and branches And simplify memory management Refs qgis#12173
conjunction with the "merge connected lines" setting Refs #12173
with line networks that contains forks and branches And simplify memory management Refs #12173
Refs qgis#12173 (cherry picked from commit 0b451b2)
conjunction with the "merge connected lines" setting Refs qgis#12173 (cherry picked from commit 7213030)
with line networks that contains forks and branches And simplify memory management Refs qgis#12173 (cherry picked from commit e0aa09c)
Author Name: Paolo Cavallini (@pcav)
Original Redmine Issue: 2113
Affected QGIS version: 3.2
Redmine category:labelling
With the new labelling engine, I always get far too few labels when selection the "curved" option. See attached screenshot an sample file.
Related issue(s): #15916 (relates), #19124 (duplicates)
Redmine related issue(s): 6763, 10740
The text was updated successfully, but these errors were encountered: