-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Decoration -> Scale Bar uses a misleading planimetric measurement #28407
Comments
Author Name: Jürgen Fischer (@jef-n)
|
Author Name: Jürgen Fischer (@jef-n)
|
Author Name: Jürgen Fischer (@jef-n)
!qgis_fehler.png! |
Author Name: Jürgen Fischer (@jef-n)
!qgis_fehler.png! to The map scale is shown wrongly - 20m instead of 12,4m. !qgis%20fehler.png! |
Author Name: Borys Jurgiel (@borysiasty) Currently, the scale bar always show planimetric distance. Especially when working in EPSG:4326 and the scale bar is displayed in metres (see also #22187), users may assume the measurement is ellipsoidal, what is not true.
|
Author Name: Borys Jurgiel (@borysiasty)
|
@borysiasty @jef-n It is so very misleading it should be at least switched off for nonellipsoidal projections. In projects in Transverse Mercartors or Lambert Azimuthal Equal Area CRS' it works correctly. |
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
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 #28407
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 (cherry picked from commit 5080eb7)
Author Name: Max Muh (Max Muh)
Original Redmine Issue: 20587
Affected QGIS version: 3.5(master)
Redmine category:decorations
The map scale is shown wrongly - 20m instead of 12,4m.
The text was updated successfully, but these errors were encountered: