-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Map rendering: Elevation markers don't respect units of length settinf #7408
Comments
I note the same thing. |
Another vote for this. It's so great to have contour lines in feet (thanks!) that now I'm getting greedy and wanting feature elevations to match the nearby contours. :-) |
I noticed the same thing in v4.8.5. Is this still an active issue? |
@groutr The issue is still open, and it is assigned to "Future-backend" milestone |
@xmd5a2 @ivanPyrohivskyi we need to generate maps with 2 text info and and have internal renderingProperty (feet / km) to display 1 text shield or another. Later UI application will pass that property to rendering engine. |
Set to |
Updated pull request: osmandapp/OsmAnd-resources#1180 |
|
Add eleUnits option and modify styles osmandapp/OsmAnd#7408
Testing 1
Version Details:
Issue Description:
Severity: Major 🟠 Visual Comparison: |
Minor issue: Currently the app displays a number next to key features like mountain peaks to indicate the elevation.
However, I noticed that regardless of the configuration of the units of length in the global settings, the map always gives those numbers in units of meters. If you are configured to use miles/feet, the elevation is still given in meters.
This can be a little confusing because the numbers are given without units (there is no 'm' following the elevation number). By contrast, the overlay that shows your current altitude both respects the units of length setting, and indicates the units within the overlay.
The text was updated successfully, but these errors were encountered: