# App: Improve rerouting at start

**URL:** <https://forum.kurviger.com/t/app-improve-rerouting-at-start/2875>\
**Category:** Implemented features\
**Tags:** implemented\
**Created:** [March 28, 2020, 6:51pm UTC](https://forum.kurviger.com/t/app-improve-rerouting-at-start/2875 "2020-03-28T18:51:33Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![linux-user](https://forum.kurviger.com/user_avatar/forum.kurviger.com/linux-user/32/56_2.png) [@linux-user](https://forum.kurviger.com/u/linux-user)\
**Post date:** [April 28, 2020, 8:11am UTC](https://forum.kurviger.com/t/app-improve-rerouting-at-start/2875/14 "2020-04-28T08:11:04Z")

</div>

> [@devemux86](#):
>
> do we need more rerouting options at start of navigation?

IMO ideally there should be no question at all at start of navigation.

If I am somewhere near the route (but not _on_ the route) maybe after a break, I want to be guided back to the route as seamless as possible.  
Whether this is “_nearest point on route_” or “_nearest waypoint_” isn’t too important. But not both.  
Keep the start menu as **simple as possible**!

Some people seem to expect _start_ as an option as well, so I would offer _start_ and **one** other option.

_nearest point on route_  
or  
_nearest waypoint_

Edit:  
Despite the issues dicussed [here](https://forum.kurviger.com/t/rerouting-problem-at-start-of-navigation/3086) I still prefer _nearest point on route_  
Edit 2:  
Maybe onother option could be “nearest unvisited waypoint”.  
So that after a break, you won’t be guided backwards, providet that the route is still in memory.

---

_[View the full topic](https://forum.kurviger.com/t/app-improve-rerouting-at-start/2875)._
