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
Change or add option to use Map Elevation #15566
Comments
The might be a slight misunderstanding with regard to what the meaning of "map elevation" is: It's not about "difference in elevation compared to current position", but "(absolute) elevation gathered by lidar data" in contrast to GPS elevation being "(absolute) elevation relativ to WGS84 elipsoid". When we introduced the elevation display, we started with "map elevation" even for current position, but that has two drawbacks:
Therefore the team decided to switch to "GPS elevation" for current position, and we adapted c:geo with the latest update. Having said that, there is a different feature which might be for you: With the latest update you can get an elevation chart for your individual route, which gives you a nice overview about elevation changes on your route. For this you need to
For a visual impression have a look at the screenshots in #14779 (comment) |
Hi. I've already tested the elevation chart, and for me works when I plan one route with c:geo, adding geocaches. But, when I use a box track recorded with my watch (amazfit GTS), the elevation chart is empty. And when hiking in mountain, it's hard to create one track adding geocaches, because most off the times its draws a straight line, messing up completely the chart, because straight lines dosen't count on the chart. Here's some examples. Empty chart with pre-recorded gpx track: Mountain: City: |
As of today, you can calculate the difference manually, by long-tapping the destination point, reading the "map elevation" value, then long-tapping current position, reading the "map elevation" value, and subtracting the two values. But from what I read from your examples, I guess you want to have this automated:
Does this describe your feature request correctly? |
Yes, that option also replaces the need to doo the mental calculation. And should support negative values. If I'm at 100 m and the destination is at 90 m, then the value would be -10.0 m |
@rouroni1 totally agree with you. The switch from "map elevation" to "GPS elevation" confused me as well. at our home town we have something between 70-80m in average. Basing on the map elevation this hight was correctly displayed everywhere. Now with the GPS elevation being set as the new default, the hight is everywhere completly wrong - in average +50m higher than it should be. So I also would like to switch back to the map elevation based hight. |
Tell us your idea!
I usualy hike when doing geocaching, and use offline Maps. And the Elevation that C:Geo uses is based in the GNSS data, but the diference is to big to map Elevation
If I'm at 100m and the summit is at 450m in the map I prefer to have the map elevation to know that I need to go up 350 m.
.
What solution would you suggest?
If it's possible add the option to use Map Elevation.
In the example picture:
Map Elevation: 12,5 m
GNSS Elevation: 70,0 m
Is there an alternative?
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: