# 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:** 2\
**Page:** 2

<div class="post-metadata">

**Author:** ![devemux86](https://forum.kurviger.com/user_avatar/forum.kurviger.com/devemux86/32/6239_2.png) [@devemux86](https://forum.kurviger.com/u/devemux86)\
**Post date:** [April 30, 2020, 6:40am UTC](https://forum.kurviger.com/t/rerouting-problem-at-start-of-navigation/3086/21 "2020-04-30T06:40:52Z")

</div>

You mean change the nearest route point to nearest turn instruction.  
Interesting idea. Though cases exist where instructions are very far.

In above example (skipping start) would mean reroute to destination.

---

<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 1, 2020, 8:50am UTC](https://forum.kurviger.com/t/rerouting-problem-at-start-of-navigation/3086/22 "2020-05-01T08:50:51Z")

</div>

> [@devemux86](#):
>
> In above example (skipping start) would mean reroute to destination.

Yes, and the resulting route (in above example), would be how a human would expect _nearest point on route_ should look like. But the above example is to short to test, as it does not have any turn instructions at all.  
The idea is, when there is a turn instruction there must be some kind of intersection as well.  
So my hope would be, that it is less likely that you are routed back and forth on the same road.  
I am aware that this is not guaranteed.

[Previous page](https://forum.kurviger.com/t/rerouting-problem-at-start-of-navigation/3086.md?page=1)
