Bug 278639

Summary:	route recalculation interval/method very poor
Product:	[Applications] marble	Reporter:	bugspamme2012
Component:	general	Assignee:	marble-bugs
Status:	CONFIRMED ---
Severity:	normal	CC:	nienhueser
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	some future version
Platform:	Unlisted Binaries
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description bugspamme2012 2011-07-27 19:05:59 UTC

Version:           unspecified (using KDE 1.2) 
OS:                Linux

took marble for a test drive, and found many issues with navigation.

the biggest problem was route recalculation, one needed to go way way off course before a route recalculation was triggered. given the speed with which routes can be calculated by monav, is it worthwhile having a route recalculation e.g. every 10 seconds? ideally if marble could determine when one went off route that would be better.

the mothod of route recalculation can also lead to delays, as marble/monav recalculates the route ignoring the direction you're travelling in. so will calculate a route in a direction behind you, which means you have to go even more out of your way hoping for a 'reasonable' route recalculation.

Reproducible: Always

Steps to Reproduce:
go off route

Actual Results:  
as above

Expected Results:  
as soon as you go off route marble recalculates the route , and the new route should be in front of you and not behind you.

Comment 1 Dennis Nienhüser 2011-07-27 22:11:46 UTC

Monav 0.4 should get support to include the current heading when calculating a route.

Determining when one goes off the route is not too easy due to GPS inaccuracies. A threshold too low would lead to many false positives. Including the current direction when determining the distance to the route makes sense though.

Comment 2 bugspamme2012 2011-07-28 00:44:19 UTC

ok, thanks.

Comment 3 Justin Zobel 2021-03-09 22:51:33 UTC

Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.