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.

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

Incorrect altitude when planning a route #21415

Open
Yaqana opened this issue Nov 21, 2024 · 3 comments
Open

Incorrect altitude when planning a route #21415

Yaqana opened this issue Nov 21, 2024 · 3 comments

Comments

@Yaqana
Copy link

Yaqana commented Nov 21, 2024

Description

I'm planning an ascent up a 955m hill along an existing path using walking profile. The altitude widget correctly detects this is the height, but the route profile shows maximum altitude at about 600m. Thus, the "uphill" value is around 30% smaller than it should be.

I have similar problem with the same path further towards another hill. I planned a lot of routes in nearby area and the elevations look reasonable on them, definitely not 30% off.

Steps to reproduce

Plan a walking route from Corryhully bothy (‎56.90381° N, 5.42896° W‎) to Sgùrr nan Coireachan top (‎56.93572° N, 5.44855° W‎)

Actual result

The altitude range is 65m-611m. The uphill value is 563m.

Expected result

The route profile should go up to 955m at the end, the altitude range should be more like 65m-955m and the uphill value at least 890m

Your Environment (required)

WARNING Crash-Logs MAY contain information you deem sensitive.
Review this CAREFULLY before posting your issue!

OsmAnd Version: 4.8.4.1
Android/iOS version: iOS 18.1.1
Device model: iPhone 13 Pro
Crash-Logs: ?
@vshcherb
Copy link
Member

@yuriiurshuliak please double check android version as well

@DmitryAlexei
Copy link
Contributor

Android task #21105

@yuriiurshuliak
Copy link

The bug has been reproduced on both iOS and Android. Below are the steps to reproduce the problem on each platform:

On iOS:

  1. Use these route coordinates
  2. Ensure the Terrain and Contour Lines data are loaded.
  3. Build the route and open the Navigation Context Menu.
  4. Check the Analysis section for the Altitude Range:
    • Result: 65m - 611m.
    • Expected: The Elevation: map center widget displays 938m, which is the correct value.

On Android:

  1. Use the same route as above.
  2. Load the Terrain and Contour Lines data.
  3. Build the route and open the Navigation Context Menu.
  4. Check the Analysis section for the Altitude Range:
    • Result: 65m - 611m.
  5. Switch to Route Planning:
    • Plan the same route and navigate to Graph → Get Elevation Data → Use Terrain Maps.
    • Result: The elevation is correctly displayed up to 938m.

This confirms a discrepancy between the route profile's altitude range and the correct elevation values provided by the widget and terrain data.

OsmAnd~ 5.0.0#3793m, released: 2024-11-25
OsmAnd 4.9.0.4

iOS Android

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants