# Rerouting problem at start of navigation

**URL:** <https://forum.kurviger.com/t/rerouting-problem-at-start-of-navigation/3086>\
**Category:** App\
**Tags:** routing\
**Created:** [April 27, 2020, 9:30am UTC](https://forum.kurviger.com/t/rerouting-problem-at-start-of-navigation/3086 "2020-04-27T09:30:43Z")\
**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, 6:00am UTC](https://forum.kurviger.com/t/rerouting-problem-at-start-of-navigation/3086/14 "2020-04-28T06:00:14Z")

</div>

![err](https://forum.kurviger.com/uploads/default/original/2X/8/827b0f1399e9a1f696cb2a8ec95d4f7a7facead2.png)

If the user would have manually set a WP at the (1) nobody would be surprised.

So the “issue” is that humans think that \*nearest point on route" should be at the intersection (blue arrow). The driver can ignore the _shaping point (1)_ and navigation should continue normally, so it is not a big deal.

I think (in theory) this could be solved with only a single route calculation.

- keep the original route in memory
- do a route calculation towards _nearest point on route_
- the point where the new route hits the original one, should be the correct place to merge the two routes.

Probably a lot of work for a simple problem.

---

_[View the full topic](https://forum.kurviger.com/t/rerouting-problem-at-start-of-navigation/3086)._
