Remaining elevation gain to a route target

Guest ●

Yes i support your idea too. Maybe some expansion of the idea:

I was wondering if it's possible to display the following info during guidance along a track: What's the distance and vertical differences (exactly: the sum of elevation meters uphill, and the sum of elevation meters downhill) to the track's destination. Maybe additionally display the chart of the remaining track.

It's possible to get these infos for tracks without guidance turned on, you just have to click on the trackline

742bcc36425afab84f56c14dd681eeee

But i couldn't figure out how to display these infos for a track which I'm actually following by guidance:

9493c98251562859f6cea35585ce4f29

Reply URL

1

Falco ●

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

Reply URL

1

Falco ●

I would vote for

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

URL

1

Bucky Kid ●

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

URL

1

Falco ●

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"

URL

1

Bucky Kid ●

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.

URL

1

Falco ●

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.

Files:

Reply URL

1

Bucky Kid ●

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?

URL

1

Henk van der Spek ●

76 is the trackpoint number I believe.

URL

1

Falco ●

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)

Reply URL

1

Marius Moldovan ●

Happy to hear that

URL

1

Falco ●

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.

URL

1

Falco ●

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.

URL

1

Falco ●

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.

URL

1

Marius Moldovan ●

Selecting track is OK..

URL

1

Falco ●

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.

Reply URL

1

Falco ●

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

Reply URL

1

Falco ●

Here it is:

https://play.google.com/store/apps/details?id=falcosc.locus.addon.tasker&utm_source=help

And here are some project examples:

https://github.com/Falcosc/locus-addon-tasker/wiki/Examples

But we have to wait for the current Locus Map beta to get the Dashboard state and the live track id.

Currently it is only useable if you manually select the track and the dashboard overlay is always on because I don't know if your dashboard is open or not on the current Locus Map version.

More examples will follow soon.

Reply URL

1

Marius Moldovan ●

Great, thank you... I'll try this till new locus version comes on-line

Reply URL

1

Falco ●

I hope you can import the Profile, because I am not sure how the plugin action code is handled for third party apps like this I didn't even use the correct signed app from google to create this profile. If it does not work, just tell me, then I will recreate it based on the playstore version. You can use my own issues page if you have any trouble:

https://github.com/Falcosc/locus-addon-tasker/issues

Reply URL

1

Marius Moldovan ●

@ Falco..

I bought your plugin and downloaded your 2 files .prf.xml and .scn.xml

Please can you tell me next steps to do in order to have this thing working?

Thanks

Reply URL

1

Falco ●

Non detailed description:

put both files on your phone
open takser scene tab and long click on tab name to import
import scene xml
open tasker projet tab and long click on tab name to import
import project (tasks get automatically imported with the project)

URL

1

Marius Moldovan ●

I imported those,activated a dashboard and started a navigation,but after I clicked Prepare remaining elevation -OK

I pressed Run task -UpdateElevationOverlay but i get an error Can't start task: No permission

Files:

URL

1

Falco ●

You don't need to use "Run Task" this is a placeholder for other ideas and require to configure tasker to allow task execution by other apps.

You did already trigger the dashboard overlay, it is the white box but your text is alot larger then my text. You can edit it at scene configuration and move it at task configuration.

According to your screenshot It does tell "noTrk". Track selection will work automatically on next locus version or you could manually select the track with prepare remaining elevation.

And as you see in the task comments, I wait for dashboard support and just enable it allways.

After the braking change you will need new project xml, for that reason you shouldn't spend to many time with the setup.

URL

1

Marius Moldovan ●

P.S. Do you have other projects involving this tasker plug-in and Locus ?!

Reply URL

1

Falco ●

Yes I have.

- Missing Elevation dashboard (this topic)

- Accurate uphill Elevation done dashboard (very advances pressure sensor calculation)

- Centre Map to GPS on move (replace for centre Map to GPS after 5s)

- locus software display lock as replacement for android display lock

Last two could be done without the plugin but the plugin make it more easy to use locus action tasks.

I will add them later. And you are on the point. I did create the 25$ Google account only for people like you. But didn't think about the the little bit complicated Tasker UI. I mean Tasker is still more easy to use then compiling my plugin from source, but for non technical people it will be still hard to understand.

I will create a screenshot manual for the project usage to make it less complicated.

Could you wait some weeks? I would prefer to get the braking plugin change done before pushing the examples because breaking version mean you have to reimport updated example projects to keep it working.

Reply URL

1

Marius Moldovan ●

What is the braking plugin change?

Is it something related to next version of Locus?

Reply URL

1

Falco ●

Not really, I did use the tasker api wrong.

But we need the next Locus version anyway to detect dashboard.

URL

1

Marius Moldovan ●

So whar would be the ETA for final version?

URL

1

Falco ●

Mid october in worst case. But will be deliverd maybe end of this month. I do have a compleate version since 3 weeks but didn't deliver it because I could find time to finish my todos. It's so old that I didn't even remember which things will not work in the current preview.

If you want, you can enter the preview, this will have the final configuration structure: https://play.google.com/apps/testing/falcosc.locus.addon.tasker

If you like you could use it and create bugs in my issue board https://github.com/Falcosc/locus-addon-tasker/issues

URL

1

Marius Moldovan ●

@Falco any news regarding new version? it's mid october.. :)

URL

1

Eddie Teo ●

I like this idea. An implementation similar to what is offered in Maps 3D would be great.

515d918d27d8874e07110c0f7b99db48

URL

1

Marius Moldovan ●

Falco. any news? at least an ETA ?

URL

1

Falco ●

I still didn't test and release the open beta from 40 days ago. But we should already have everything we need from locus.

URL

1

Marius Moldovan ●

Locus implementation is ready, but your plugin still cannot fully function until you implement latest beta version, this is what you are saying?

But you don't have time still to work on it now?

Then in how much time..

I liked your work (examples)

URL

1

Falco ●

I don't want to tell that this unreleased version do work: https://play.google.com/apps/testing/falcosc.locus.addon.tasker

After I did confirm it I will release it and export examples as well. But this week I am still on vacation. Sorry for the delay.

URL

1

Marius Moldovan ●

No problem.. Enjoy your vacation

There's time next week also

URL

2

Talbi ●

Would it be possible to implement this in dashboard (and not only for navigation)?

I can't believe all the outdoor freaks are not interested in such feature!?

Elevation meters uphill (and also downhill) to the tracks destination is such a helpful information.

Reply URL

2

Marius Moldovan ●

+1 .. Want it too

URL

1

Bernhard Friess ●

+1 Want it too!

URL

1

Tapio ●

OP is absolutely right. This is also desperately needed in the track management, being able to sort by elevation gain (uphill). For everyone doing training, the most important information beside the track length.

http://help.locusmap.eu/topic/data-manager-sort-order-for-tracks-elevation-uphill

URL

1

Igor Martić ●

+1 Would like to see this implemented, when navigation or guidance is active elevation profile graph is visible in the bottom, along with some POIs if track contains them.

Reply URL

1

Guest ●

Hello, yesterday I was doing a cycle tour using Locus to navigate to a final point. During the steep uphill part I wanted to know how many "Elevation loss" and "Elevation gain" still ahead of me, besides the horizontal distance to the finishing point when I click onto "Information". I couldn't get this information from my current location by clicking on the track line - just the overall values from the starting point of the route.

I've done some research, and there are already some other threads too which are proposing this feature or some similar feature using dashboard and/or Navigation top-menu to display these values, with in total quite a few "Likes". Would be a great improvement during Sports-Navigation if this would be implemented.

https://forum.locusmap.eu/index.php?topic=5772

https://help.locusmap.eu/topic/dashboard_add_vertical_distance_to_target

https://help.locusmap.eu/topic/navigation-panel-request-for-new-field-vertical-distance-to-target

https://help.locusmap.eu/topic/elevation-to-target

Reply URL

1

zossebart ●

As a MTBiker, I also would love to have upcoming elevation gain/loss available in nav display and as dashboard items! After remaining track length, this is the second most important information we need when navigating a track.

As you have this information available in the popup when selecting a point on a track, I think it shouldn't be too difficult to make this information also available in dashboards/the navigation top bar? Is it?

Reply URL

2

Michal Stupka ●

Hi,

remaining elevation gain (both positive and negative) is displayed in the popup box when you tap the route on the main screen:

fb8a8c237af43f0230dc84546ca821c8

best regards

Michal

Reply URL

2

wiener30 ●

Thank you.

It would be much more convenient to have it as a dashboard item.

Could it be added to the list of dashboard items as an upgrade of the app.

URL

2

zossebart ●

I think this was discussed before, but I don't remember the conclusion.

@Locus-team: Could you please describe again, why it's not possible to add remaining elevation gain/loss as dashboard items? Locus clearly has no problem calculating these values and shows them on track popup and in tracks list.

Falco even implemented a way to overlay elevation gain using Locus API/Tasker, but it would be far more easy if this was builtin to Locus.

I think lots of sports enthusiasts ((mountain-)bikers, hikers, trailrunners?) would love to have these values in dashboards.

Maybe the problem is the discrepancy between theoretical values from the track and the live values from gps recording which are only corrected (if configured) after the track recording?

URL

1

Guest ●

There it's been discussed:

https://help.locusmap.eu/topic/upcoming-elevation-gain

Reply URL

1

zossebart ●

Thanks! It seems there was no definite answer from Locus-team in this discussion (and the others referenced there), either?

URL

1

Talbi ●

How much votes are needed, Menion and Locus-team will respond (or even implement) this idea?

Reply URL

2

Menion ●

Hello,

as I see, there is already the reponse from @Michal Stupka (part of the team).

Anyway, choosing of the topic to implement is complicated to be true. There is no strict mechanism and topics directly related to Locus Map are usually choose based on many factors that combine in my head.

In this case: detail of track will receive during the next few months major update. I'll try to keep this legit requirement in the head during the process of re-creating.

URL

1

Tapio ●

Currently there's the audio trainer basically telling about past achievements, because it's related to recording.

As an addition, I wish there were the same tts possibilities for forward looking, i. e. related to current guiding. Like discussed here. TTS could say "Remaining uphill: 123 meters".

It could happen timed, every n meters flat, every n meters gain-, every n meters gain+. The variables are clearly there...

I know, I'm annoying. But often was thinking that would be nice 😊 I see Software development is a can of worms...

URL

1

Hans Castorp ●

This already works, doesn't it? At least it does for me for tracks.

If you tap on a location on a the track, you'll get the "Track Details" popup, then I tap on the ">" arrow and the following popup menu contains a menu item "Elevation diagram at point" which will show an elevation diagram with the point selected track point

It's not exactly the same as requested, but for me this works good enough

Files:

URL

1

blahdi ●

fyi-this idea is a combined idea that tracks displaying the information on dashboard.

If too many keys have to be pressed to get the answer, it isn't usable in the wilderness.

URL

1

joeloc ●

Sponsoring a mountain bike for Locus Team might work... to guide development in a more outdoorsy direction. The last years we're more oriented towards tupperware box seekers... which unfortunately seem to be the majority among users :)

URL

2

Viajero Perdido ●

Hey. Some of us tupperware seekers actually hike up mountains with a good map in our hands. Some even update OSM in advance of next year's expeditions, then wait patiently for offline map updates. :)

URL

1

Talbi ●

Hi guys!

Maybe you want to vote for this idea:

https://help.locusmap.eu/topic/upcoming-elevation-gain

It is exactly the same topic.

Reply URL

1

Lucas Heiss ●

Are there any news about this topic? May we hope for a feature like this in the future? :)

Reply URL

1

Eddie Teo ●

Will we ever see this feature implemented now that Locus Map 4 is officially released? Pretty sure this doesn't require rewriting the whole app core, or does it?

Reply URL

1

zossebart ●

+1

as was probably said before, also a very useful information for mountainbikers. Please consider implementing it.

Reply URL

2

Thermostat ●

Another +1 here.

I sorely miss seeing the remaining height to climb when I can quickly know I may have just 10km to go in the evening on my mountainbike, but if that includes 500hm, I might just call it a day.

I can't really use the heightmeters traveled so far on GPS to track what's left, as that is quite inaccurate/different from what is calculated from the track.

I miss it most when following the line of a long multi-day track, and having to check the remaining heightmeters of both my expected endpoint and my current point, subtract, and get the desired number.

Furthermore, it would be great to see both the gain and loss in a glance. So for example the top bar can have the remaining distance in one slot, and the remaining height gain and loss divided by for example a "/" in the other.

Reply URL

1

Lucas Heiss ●

+1 :)

URL

1

Tapio ●

Glorious idea (not sure 😁) here: What if LM offers hm markers just like the distance markers, same behaviour?

Reply URL

1

Lucas Heiss ●

I think that's a great idea – in addition to the display of the remaining height gain on the dashboard!

URL

1

Karl ●

would be a great idea to add the remaining height to the dashboard possibilities.

I am astonished that not much more people want that implemented.

Reply URL

1

Rafał Nowak ●

Exactly. Seems like simple addition. They have estimated elevation left to target when you click on track point and implemented in dashboard. Looks like nobrainer.

URL

4

Menion ●

Hi guys,

remaining elevation gain/loss will be added as another option for the dashboard in the next Locus Map 4.26 version.

I had to make quite a lot of changes to the background to make this possible. So even if heavily tested, expect that in the first version may be some issues. Just a small warning :).

9005d7a73e0ba2d5f40903a6737f6602

Reply URL

1

Tapio ●

Now if this is available for dashboard, can you make it available for the audio trainer?

URL

1

Menion ●

Hmm this is a problem. An audio coach is not made for the navigation system. You may see, that there are no variables from the navigation, only variables related to the running track recording (and few basic global variables).

It is anyway an interesting idea > to integrate some navigation variables into Audio Coach as well ...

URL

2

Tapio ●

Yes, now I remember. Same as with dashboards (which shows nav related data, but sometimes there is no navigation), audio trainer could make all the interesting stuff avaliable. And not read out if data is not existing.

URL

1

Waldemar Wawoczny ●

Hi,

do the dashboard items: [Remaining elevation gain] and [Remaining elevation loss] refer to VERTICAL elevation, or do the values displayed tell us: how far we have to cycle downhill/uphill [m or km]?

And it looks to me like these are VERTICAL values, which is abstract to me. I would prefer how much I have to cycle uphill/downhill.

Waldek

Example of a very short 6 km route
Locus: elevation loss -69.91 m / distance from above 898.7 m,
according to BRouter: Elevation gain 2 m / Height difference -60 m.
Dashboard: Remanining elevation loss -76.52 m
So, nothing adds up!

Reply URL

1

Menion ●

Hello Waldemar,

yes, these values are vertical remaining elevation gain/loss as these are generally more important during the ride. There already exists a "Distance to target", so you can have a basic idea of the remaining distance, but till now, there was no option to know the remaining elevation.

I do not fully understand your "example". Maybe some screenshots or a better description is needed, if you consider it as important. Thanks.

URL

1

Waldemar Wawoczny ●

Hi,

I'm translating: Locus: elevation loss -69.91 m and Dashboard: Remaining elevation loss -76.52 m - should they be equal?

I'm thinking about why it's so important?
I didn't really follow it, but maybe an example:
I have Remaining elevation gain = +200 m on a 10 km section
and now: if the slope is uphill along the entire length, it will be quite a pleasant ride, but if, for example, the slope is + only on a 3 km section, it will be a tragic climb, even though it will be flat (zero) later.
Can you explain this to me?

waldek

URL

Remaining elevation gain to a route target

Merged Objects

Upcoming elevation gain

Elevation gain/loss to destination in dashboard?

Add remaining elevation gain to a route end to the dashboard

Replies (29)