# App: Improve rerouting settings

**URL:** <https://forum.kurviger.com/t/app-improve-rerouting-settings/3107>\
**Category:** Implemented features\
**Tags:** implemented\
**Created:** [April 21, 2020, 6:27am UTC](https://forum.kurviger.com/t/app-improve-rerouting-settings/3107 "2020-04-21T06:27:48Z")\
**Posts on this page:** 1\
**Showing post:** 6

<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 21, 2020, 2:25pm UTC](https://forum.kurviger.com/t/app-improve-rerouting-settings/3107/6 "2020-04-21T14:25:29Z")

</div>

> [@radek.rehorek](#):
>
> But it often tries to return me to point that is behind my bike

This is another reason why I [suggested](https://forum.kurviger.com/t/app-rerouting-options/1934/15) to remove “Nearest point on route” from re-routing options.  
I would instead keep “Nearest point on route” as an option at [start of navigation](https://forum.kurviger.com/t/app-rerouting-options-at-start-of-navigation/2875/7)

This way you can still use this routing option, without complicating the app unnecessarily.  
IMHO “Nearest point on route” makes more sense at start of navigation, than as an option for automatic recalculation.

---

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