Remaining elevation gain to a route target

Bucky Kid shared this idea 4 months 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 (36)

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

photo
1

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.

photo
1

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

photo
1

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

photo
1

@ 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

photo
1

Non detailed description:

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

photo
1

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

photo
1

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.

photo
photo
1

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

photo
1

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.

photo
1

What is the braking plugin change?

Is it something related to next version of Locus?

photo
1

Not really, I did use the tasker api wrong.

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

photo
1

So whar would be the ETA for final version?

photo
1

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

photo
1

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

photo
1

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

515d918d27d8874e07110c0f7b99db48

photo
1

Falco. any news? at least an ETA ?

photo
1

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

photo
1

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)

photo
1

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.

photo
1

No problem.. Enjoy your vacation

There's time next week also

photo