This object is in archive!
Navigation doesen't start at the start-position which I choose
Solved
Good day,
if I start an navigation, and the start position isn't my current GPS position, the navigation won't start at the start position I choose. Here is an example:
the navigation doesen't start at the start position.
This problem exist since all Locus versions, that i used, so it's really time to fix this
The same problem 
Good day Nicolai,
"problem" is not fixed, because at least I do not consider this as a problem.
Navigation purpose is to navigate along defined path to your target. In this case, you started navigation a far far away from your route, so Locus try to find nearest place where you may continue to your desired target!
In case, you wants to navigate along the route since start, why you start navigation like on screenshot, instead of firstly ride by any method to start point (like by navigation to start point) and then start navigation along route?
Good day Nicolai,
"problem" is not fixed, because at least I do not consider this as a problem.
Navigation purpose is to navigate along defined path to your target. In this case, you started navigation a far far away from your route, so Locus try to find nearest place where you may continue to your desired target!
In case, you wants to navigate along the route since start, why you start navigation like on screenshot, instead of firstly ride by any method to start point (like by navigation to start point) and then start navigation along route?
Hmm I don't understand your answer.
One more example to my problem:
Tomorrow I want to go to the city Karlsruhe and after the city Trip in Karlsruhe I want to drive to Stuttgart. Now I want to know, how long I have to drive from Karlsruhe to Stuttgart.
And thats the problem. If I set Karlsruhe as navigation start point, the navigation won't start at Karlsruhe, and so the time, that I'll need from Karlsruhe to Stuttgart won't be correct.
Hmm I don't understand your answer.
One more example to my problem:
Tomorrow I want to go to the city Karlsruhe and after the city Trip in Karlsruhe I want to drive to Stuttgart. Now I want to know, how long I have to drive from Karlsruhe to Stuttgart.
And thats the problem. If I set Karlsruhe as navigation start point, the navigation won't start at Karlsruhe, and so the time, that I'll need from Karlsruhe to Stuttgart won't be correct.
Hello Nicolai,
understand. So main problem here is measuring of estimated travel times, hmm. As @0709 wrote, one option to get estimated times is using specialized function for this task. This anyway works only for a foot & bike, not for other transport vehicles, like car.
From my point of view, Locus now works correctly. You wants to navigate to your target and Locus tries to find best place (nearest) where to start. Understand that it's little bit weird when you are 100 km away. On second side, for me is weird as well, why to start navigation when you are 100 km away.
So what you miss here is an option to see estimated travel time for computed track without need to start navigation, right? Also some more clever selecting of "nearest point" should be used here, like "when more then 1 km away from nearest point, navigate to start instead".
EDIT: oki, I'll improve it little bit to next version.
Hello Nicolai,
understand. So main problem here is measuring of estimated travel times, hmm. As @0709 wrote, one option to get estimated times is using specialized function for this task. This anyway works only for a foot & bike, not for other transport vehicles, like car.
From my point of view, Locus now works correctly. You wants to navigate to your target and Locus tries to find best place (nearest) where to start. Understand that it's little bit weird when you are 100 km away. On second side, for me is weird as well, why to start navigation when you are 100 km away.
So what you miss here is an option to see estimated travel time for computed track without need to start navigation, right? Also some more clever selecting of "nearest point" should be used here, like "when more then 1 km away from nearest point, navigate to start instead".
EDIT: oki, I'll improve it little bit to next version.
Also some more clever selecting of "nearest point" should be used here, like "when more then 1 km away from nearest point, navigate to start instead"
I do not like this suggested solution. As it destroys actual version nice behaviour = Picture nr 3 navigate.
Prefer actual flexible easy fast (re)join navtrack to nearest trackpoint even if positioned further away from track.
Touring and leaving long navtrack for any reason for a longer time, to >> 1km hotel/sleep, so Locus navigate off,.
Next morning restart navigate Locus should not navigate back to start, but toward nearest trackpoint.
Start 100 km away from track, Locus navigate to start, to be solved by other method.
Propose:
Any navigation track always to obtain a Start (Priority) Point ! (rtePointAction>50 = not 1)
Push select track near start position -> Locus select option: "Navigate track" or "Navigate to" Start Point.
If navtrack has additional "Priority Points" any such point can be selected for a direct "Navigate to".
Picture example:
A roundtrip by "Knoopunten" system. Track source by external website.
All 'Knooppunten" are Locus "Priority Points" inclusive "Start 71".
1. User position about 2 km away from closest trackpoint
2. Push track near start: Locus present options: Navigate track: 'Rondje knopen" OR "Start 71" OR "Finish 71".
3. Navigating track: "Rondje knopen" Locus Navigates toward nearest point, to next Priority Point "33", than follow track design up to to "Finish 71".
4. Navigation to Point: "Start 71". Locus (Fast bike) Navigates direct toward "Start 71".
Also some more clever selecting of "nearest point" should be used here, like "when more then 1 km away from nearest point, navigate to start instead"
I do not like this suggested solution. As it destroys actual version nice behaviour = Picture nr 3 navigate.
Prefer actual flexible easy fast (re)join navtrack to nearest trackpoint even if positioned further away from track.
Touring and leaving long navtrack for any reason for a longer time, to >> 1km hotel/sleep, so Locus navigate off,.
Next morning restart navigate Locus should not navigate back to start, but toward nearest trackpoint.
Start 100 km away from track, Locus navigate to start, to be solved by other method.
Propose:
Any navigation track always to obtain a Start (Priority) Point ! (rtePointAction>50 = not 1)
Push select track near start position -> Locus select option: "Navigate track" or "Navigate to" Start Point.
If navtrack has additional "Priority Points" any such point can be selected for a direct "Navigate to".
Picture example:
A roundtrip by "Knoopunten" system. Track source by external website.
All 'Knooppunten" are Locus "Priority Points" inclusive "Start 71".
1. User position about 2 km away from closest trackpoint
2. Push track near start: Locus present options: Navigate track: 'Rondje knopen" OR "Start 71" OR "Finish 71".
3. Navigating track: "Rondje knopen" Locus Navigates toward nearest point, to next Priority Point "33", than follow track design up to to "Finish 71".
4. Navigation to Point: "Start 71". Locus (Fast bike) Navigates direct toward "Start 71".
Replies have been locked on this page!