Use a proper ellipsoidal length calculation when calculating the size of the scalebar decoration #37084
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
calculating the size of the scalebar decoration Avoids a misleading Cartesian-based scalebar (unless project is set to always use cartesian measurements, that is!) Fixes qgis#28407
|
Hi @nyalldawson, is it possible this be the cause of the #40748 issue (which occurs for QGIS ltr >= 3.10,8 and QGIS pr >= 3.14.0)? |
|
@agiudiceandrea it's possible -- but prior to this the scale bar results were misleading anyway, so it would be tricky to test. That issue description makes it sound like there's a missing connection or signal causing the bar to update... |
|
Not so misleading... with 3.10.7 with 3.10.8 with 3.10.8 after zoom in and then zoom last |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Avoids a misleading Cartesian-based scalebar (unless project is
set to always use cartesian measurements, that is!)
Fixes #28407