# 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:** 18

<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:** [May 2, 2020, 5:53pm UTC](https://forum.kurviger.com/t/app-improve-rerouting-at-start/2875/18 "2020-05-02T17:53:00Z")

</div>

> [@devemux86](#):
>
> everywhere, falling back to:
> 
> - Start
> - Nearest waypoint

Probably the easiest way.  
The beauty of “nearest waypoint” is, that users would understand what is happening, and probably don’t complain - even if they might not like the result.

##### My concern is the following situation:

At a break along the route, I would stop navigation and maybe even close the app.  
My position may be 100m away from route.  
Then when I start navigation again, app may route back to a waypoint I have already visited, because the history of visited waypoints has been lost then.  
The “nearest waypoint” may be many km back.

“Nearest point on route” would route back only a few 100m, even [in corner cases like here](https://forum.kurviger.com/t/rerouting-problem-at-start-of-navigation/3086/14)

---

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