[go: nahoru, domu]
Skip to content
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.

Sign up for GitHub

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

Jump to bottom

ScaleBar has up to 100% error #233

Open
bubenheimer opened this issue Nov 30, 2022 · 0 comments
Open

ScaleBar has up to 100% error #233

bubenheimer opened this issue Nov 30, 2022 · 0 comments
Assignees
@DSteve595
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@bubenheimer
Copy link
Contributor

Maps Compose 2.7.2

Looking at the ScaleBar demo I notice an up to 100% error in the length of the ScaleBar vs. the displayed length value: For example, at the 1000m mark, the ScaleBar label switches to "1 km" until it reaches 2000m/2km, with a constant ScaleBar length.

Maps generally operate in the GIS realm, and a user would have a reasonable expectation of correctness.

I believe Google Maps addresses this issue by using variable length scale bars, which I'd think is what needs to be done instead.
@bubenheimer bubenheimer added triage me I really want to be triaged. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. labels Nov 30, 2022
@DSteve595 DSteve595 added priority: p2 Moderately-important priority. Fix may not be included in next release. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. and removed triage me I really want to be triaged. priority: p2 Moderately-important priority. Fix may not be included in next release. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. labels Dec 12, 2022
@DSteve595 DSteve595 self-assigned this Jan 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@DSteve595 DSteve595

Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bubenheimer @DSteve595