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

Change or add option to use Map Elevation #15566

Open
rouroni1 opened this issue Apr 6, 2024 · 5 comments
Open

Change or add option to use Map Elevation #15566

rouroni1 opened this issue Apr 6, 2024 · 5 comments
Labels
Feature Request A request for a new feature/function Unverified Issue not yet confirmed/reproduced or feature requests not yet checked for plausibility

Comments

@rouroni1
Copy link

rouroni1 commented Apr 6, 2024

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.

Screenshot_2024-04-07-00-16-28-242_cgeo geocaching
.

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

@rouroni1 rouroni1 added Feature Request A request for a new feature/function Unverified Issue not yet confirmed/reproduced or feature requests not yet checked for plausibility labels Apr 6, 2024
@moving-bits
Copy link
Member

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:

  • "map elevation" is gathered from underlying map data and is a costly operation (which lead to significant delays in map display for some), whereas "GPS elevation" comes (more or less) "for free"
  • "map elevation" and "GPS elevation" have different values in many places. On c:geo mainscreen we display "GPS elevation" for current position, so it might be confusing if we displayed "map elevation" for current position on the map.

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

  • use UnifiedMap (it's only implemented in that map type)
  • create an individual route
  • tap on the individual route

For a visual impression have a look at the screenshots in #14779 (comment)

@rouroni1
Copy link
Author

rouroni1 commented Apr 7, 2024

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:
https://github.com/cgeo/cgeo/assets/27059385/06c527ce-718f-4095-9e22-86f8be0fccb4

Mountain:
https://github.com/cgeo/cgeo/assets/27059385/61780a60-5333-49e0-95f6-6bfd0d9655c2

City:
https://github.com/cgeo/cgeo/assets/27059385/114380f9-2afc-4def-af5f-82bb35d3f5b4

@moving-bits
Copy link
Member

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:

  • if this feature is activated (eg: "show map elevation difference to target"), and
  • if a target is set (red line to destination)
  • and map supports elevation data (not all do)
  • then display the differences in map elevation between set target and current position below the blue position marker

Does this describe your feature request correctly?

@rouroni1
Copy link
Author

rouroni1 commented Apr 7, 2024

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

@wolverine007
Copy link

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Request A request for a new feature/function Unverified Issue not yet confirmed/reproduced or feature requests not yet checked for plausibility
Projects
None yet
Development

No branches or pull requests

3 participants