Remaining elevation gain to a route target

Bucky Kid shared this idea 4 weeks ago
Collecting votes

Hello, could you display remaining ascent to route end based on selected point of track display ?

I'd appreciate to add this computed value to point details (and also to displayable dashboard items).

Elevation to target is as important as distance to target to better estimate time to finish.

Comments (16)

photo
1

We do already have this value, we just need it as an dashboard element and as navigation element.


I have to disable navigation everytime be able to touch the track to get the small track popup with remaining elevation gain to the end of track.


But there is one problem which need to be discussed:

What should happen if we are not on track?

for Distance it's easy: remaining track distance + distance to closest track point

But what do we want to display for elevation if we are not on track?

  • remaining track elevation + 0m (nothing required)
  • remaining track elevation + SRTM elevation on straight line to closest track point (requires SRTM)
  • remaining track elevation + altitude difference to closest track point (nothing required)
  • remaining track elevation + SRTM elevation on route to closest track point (requires navigation, route data and srtm)

remaining track elevation + 0m is what we already have in locus if we use the workarround of disabling navigation and touch the point on track to get the popup

photo
1

I would vote for

"remaining track elevation + altitude difference to closest track point (nothing required)"

photo
1

Sorry but I can't find this value even if navigation is off. If I get details of point on track I get altitude, distance from start and distance to end.

I have the elevations missing.

Also you're right in dashboard repository this value is not available íwhere it would be most useful).

photo
1

For which of the 4 solutions would you vote, because this value can't be implemented without having a solution for "I am not on the track"

photo
1

Remaining track elevation + SRTM elevation on route to closest track point

Also remaining overal elevation was meant as route elevation (SRTM), not the altitude difference between current point on track (GPS) and track final point.

Dashboard repo already has altitude difference to nearest trackpoint.

photo
photo
1

Here is the workarround:

Quit navigation / guiding

Click on the track

You get the following popup

14c18df7c61d08e9e5442c7976e0ee1d

8.5km done

50.8km left

1377hm uphill left

1668hm downhill left


But I don't know what 76 mean, 432m is the altitude of the selected point.

photo
1

I see now. That's what I was looking for.

Now how to display this parameter also live (during navigation/guiding) if dashboard misses the repository?

photo
1

76 is the trackpoint number I believe.

photo
photo
1

If this did not get enoght votes, I may be able to implement this as addon. There are many things missing to do that over Locus API but if I find the guiding track by searching for Track.isSelected() - in case this really works - and check if the UpdateContainer.getGuideTypeTrack().getNavPoint1Loc() is available at Track.getPoints() to get the current location index on track.

If I have this point I could iterate all points to target and add the positiv elevation change. It's difficould to get the direction of the guide, because you can navigate track reverse. But with UpdateContainer.getGuideTypeTrack().getTargetLoc() I could find out if this is the first or last point of the track to interate forwards or backwards.


If this idea did not get planed for 2018 I would add this to my Locus geeks collection for customization nerds and place it on my dashboard, maybe even with a real dashboard integration (http://help.locusmap.eu/topic/addonapi-for-dashboard-to-display-custom-data)

photo
1

Happy to hear that

photo
1

Wouldn't be a great solution, it would be something with 1-5 minutes refreshtime because this would be way to expensive search track again and calculate all points every second. The main problem is to find the track of the guide, because you may have more then 1 track visible and the Track.isSelected() does may not work for tracks on map.

if everything goes wrong the workarround will only work if there is only 1 visible track nearby the guiding/navigation track. But I will implement this anyway because I need it too.

photo
1

No, the API does not allow to seach for tracks, the data provider what to have an id becuase it does filter like that "track/#"


But If you know the track Id I may be able to caluculate the rest of it.

photo
1

Would it be ok for you if you need to select the track which you would like to follow? If the selected track does not match the guiding the workarround would display an error.

photo
1

Selecting track is OK..

photo
photo
1

Tasker integration could look like this:

58306775c9ca437ec7bb3bae8e58074b

01c87812de6152e70b4ebd41ac2eb5a4


Some spelling issues there, I know.

It is only a bit of error handling missing and some testing. But it should work, if you select the track manually like in the pictures I should get anything else with the API.

photo
1

The new API does now include the navigation track id, which means we can skip the manual track selection :)