Distance to specific point in navigation mode

Marius Moldovan shared this idea 18 months ago
Collecting votes

When I'm in a navigation to a point,sometimes I want to check what is the distance from my gps position to a specific point ahead my line of navigation


I click on the point but there is no information how far the point is from me,following the computed navigation path, (only altitude and gps coords are displayed)

Also the estimated time to travel to it would be nice information in contextual menu of point

It should be the same as on an already saved track, where it is already implemented this kind of information if I click on some point inside the track

Comments (12)

photo
1

I see that in new version something from this request is implemented, but when I click on a point, the distance to start and the distance to the end of computed navigation/guidance track is displayed


More usefull information would be the distance from the current GPS position to that point and the time estimated to arrive to that point.This way somebody would know how far and how much time to arrive to a chalet/hut/refuge/POI.

Current distance of point from start of the track is not giving much usefull information on arriving to that POI

photo
1

Yes, there are similar topics with this request.

Except the last one in DE forum which I cannot read(do not dpeak DE)

And what do you want to point out?

I know that in the last version you can choose 2 points on the track and Analyze.. but my request is when you compute a new route(with planner for ex.) and you begin NAVIGATION this new route. Will I then, be able to select 2 points and know the distance between them and also the time needed to navigate between this 2 points? I think not..

Feature is available now only with already recorded tracks, isn't it?

The same would be usefull for routes to be navigated

photo
1

I know, only partly fullfills wish, therefore +/- similar.

Actual Locus version: Start Navigation:

Tap Navigation Icon -> Tap Route List:

Shows the Navigation and "User Planned" Via Points distance totals.

Time ? How fast will you travel ? A guess by the Locus "snail speed" standard ? ;-)

- Generated track/routetimestamps by Locus do represent an EXTREMELY LOW speed, so can't be used the way you describe :-((

- Contrary to the correct timestamped trkpt's in a trackrecord.

[DE] => [EN]

http://docs.locusmap.eu/doku.php?id=manual:user_guide:functions:navigation

- Distance to target (3) (default)

- Time to target (4) (default) - estimated time calculated upon your average speed

- Time of arrival - estimated arrival time calculated upon your average speed

* Distance to next Via Point (NEW)

* Time (estimated) to next Via Point (NEW)

- Time to next junction - time to the next crossroads where the direction will be changed

- Time - device clock

- Altitude - current altitude of the user, calculated from GPS or the device barometer

- Speed - current speed

Anyway ...succes with idea proposal... ;-)

photo
1

"(time ? How fast will you travel ? = a guess...contrary to a trackrecord = known by the recorded trkpt timestamps)"

Well, in navigation the same principle can be applied. The time to the next via point(or any two user-defined points along the route) can be estimated using the average moving speed from the beggining of the navigation action till current time when user is trying to measure distance/time between 2 points belonging to the actual route(which is being navigated)

I hope @menion would reconsidere an old discussion about estimating time to arrival to a via point/ average moving speed calculated from the begining of navigate route(not only for the last 10-15 minutes or so)

photo
1

OK Marius... I think as in previous NEW * by "estimated" should do the job.

My point was...tapping a designed track by 2 free track/ route points ( method you described) is not representative because of these 'strange' generated timestamps.

photo
1

yes, if next Locus version will implement these 2 NEW Distance to next Via Point (NEW)* Time (estimated) to next Via Point (NEW) then situation will be a little better.

But according to the manual ,there are only two adjustable fields (3,4) which could display either distance and time to destination, OR Distance to next Via Point (NEW) and Time (estimated) to next Via Point (NEW) and I need both these informations..There cannot be displayed 3 fields in navigation, so I think it should be find a better option for displaying this extra information about ditance / time to via point..Maybe in Route/Navigation menu, something similar to Analyze option(like Distance/Time to a VIA)

My proposed method of 2 freely choosed route points is a generalisation, because sometimes I need to know how much time/distance I will need to travel between 2 FUTURE points in the route(distance between a future spring,water source and the next challet).... so Locus will compute the distance between points and then time to travel that segment will be: distance divided by average MOVING speed

Not to mention the extrastep of adding a VIA point just for measuring time/distance along that segment

I do not understand what do you mean by 'strange' generated timestamps

photo
1

Aaahh... old problem old help topic.

http://help.locusmap.eu/topic/locus-and-turtle-speed-not-a-direct-real-problem-but-o-soo-strange

Turtle speed mentioned is even very optimistic, too fast, snail speed better expression ;-)

http://forum.locusmap.eu/index.php?topic=5987.msg49876#msg49876

IF ! If Locus would ever generate +/- representative timestamps in a designed track/route according to the activity set at the route planning stage, than your suggested method would be absolutely usable (before movement and avg happens) ...of course.

Roger ?

photo
1

OK ...understand .Now we should wait for developer ,maybe he will make it happened

photo
1

Hi Marius, I was thinking about your previous note.

I know that in the last version you can choose 2 points on the track and Analyze.. but my request is when you compute a new route(with planner for ex.) and you begin NAVIGATION this new route. Will I then, be able to select 2 points and know the distance between them and also the time needed to navigate between this 2 points? I think not.


Using a route design generating timestamps based on a set constant speed can't be a very correct reference. As cycling in hilly (mountain) regions speed is very variable cycling up or down. So timestamps should be generated by a dynamic system that couples speed with the known predictable % Slope figure by the elevation data. As every person is different such a time estimate should even be personalised for a best time reference. System should be able to be (re)calibrated, so personalised for a best optimal time prediction estimates. No ?

As I prefer the Locus forum for disccussion I prepared you a short idea description.

See you in the forum ? http://forum.locusmap.eu/index.php?topic=5953.0

photo
1

Nice proposal

I like the ideea.This should give the best time estimate for current navigation track

photo