Recalculate/reroute navigation with add/remove route points

Robert Teterycz shared this idea 2 years ago
Collecting votes

I frequently use navigation while biking. Sometimes I need to reroute to shop or bar which is far from original route and back to original planed points. It is different way and need to recalculate. I do it by canceling navigation and then add new and previous points. It would be better to recalculate / reroute with change or remove current points option or just use different calculation of route fast bike... when I'm tired.

Comments (6)

photo
1

Hello Robert

if you use BRouter you can recalculate your route while navigation, additional you can set e.g. "via points" and "no go areas"

A possible solution for something similar your task i described

http://help.locusmap.eu/topic/blocked

one little bit hidden option you get on long click on "recalculate" button, then it´s possible to change the routing profile ;-))


Wolfgang

photo
1

Thanks Wolfgang. I learned new option with fast points, but recalculate option is not working. works calculation by BRouter as application but not in my Locus Map Pro.

photo
1

IMHO, Fast points need lauching BRouter application and importing the new GPS route to Locus.


I would personally use switching to simple navigation directly to that new point, and that I would return to the original route with route priority recalculation .

photo
1

I support the original idea. That BRouter workaround is imho inadequate. Almost as complicated as starting a new navigation, and totally "unorganic" in Locus.

photo
1

Having the possibility to add waypoint when navigation is already turned on is essential for me. Google maps can do it, mapy.seznam.cz can do it, why not Locus? For me it is a common pattern – to go from A to B and then reaize I need to do something in place C which is alongthe way but slightly off the course. I do not want to stop navigation and enter the new start and end… just to add a place in the middle.

photo
1

I agree that relaunching the route calculation procedure(*) with previously provided points(**) and the newly inserted viapoint makes sense and would be a useful feature.

IIRC, there are only 2 supported viapoints in the standard navigation/routing interface, so I need to bear it in his mind, or there can be a refusal. Most services do not support viapoints, so routes are calculated per route segments. I am not sure how the online services like paid Mapquest or free Yours/OSRM evaluate the request traffic, if by data volume, or by request counts. The latter could be reason for Menion not to allow too many viapoints.


(*) - as that will be needed

(**) - probably with the current position as the start