# Rerouting heading

**URL:** <https://forum.kurviger.com/t/rerouting-heading/8918>\
**Category:** App\
**Tags:** routing, problem\
**Created:** [July 25, 2022, 8:43pm UTC](https://forum.kurviger.com/t/rerouting-heading/8918 "2022-07-25T20:43:12Z")\
**Posts on this page:** 1\
**Showing post:** 7

<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:** [July 26, 2022, 3:31pm UTC](https://forum.kurviger.com/t/rerouting-heading/8918/7 "2022-07-26T15:31:11Z")

</div>

> [@Routing heading](https://forum.kurviger.com/t/routing-heading/5289/11):
>
> Unfortunately, we currently don’t have the option to provide nice u-turn announcements where we search for a good intersection to turn around.

You don’t need to search for a good intersection.  
A simple u-turn announcement if [routing headig](https://forum.kurviger.com/t/routing-heading/5289) differs too much from calculated route would improve turn instructions a lot.

Another crude idea would be, to “throw” a shaping point in front of the vehicle.  
Something like this:  
[Route with heading 270°](https://kurv.gr/a9JxS) and a shaping point in direction of vehicle movement.  
This way at least a u-turn announcement is created.

---

_[View the full topic](https://forum.kurviger.com/t/rerouting-heading/8918)._
