# Find Dead-Ends With Enabled U-Turns

**URL:** https://www.waze.com/discuss/t/find-dead-ends-with-enabled-u-turns/52824
**Category:** WME Feature Requests
**Created:** [December 26, 2013, 4:52am UTC](https://www.waze.com/discuss/t/find-dead-ends-with-enabled-u-turns/52824 "2013-12-26T04:52:36Z")
**Posts on this page:** 12
**Page:** 1

<div class="post-metadata">

### Author: ![pumrum](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/p/FF5252/32.png) [@pumrum](https://www.waze.com/discuss/u/pumrum)
#### Post date: [December 26, 2013, 4:52am UTC](https://www.waze.com/discuss/t/find-dead-ends-with-enabled-u-turns/52824/1 "2013-12-26T04:52:36Z")

</div>

Similar to Shift-Z which shows all disallowed turns, it would be helpful to be able to highlight all dead-end segments (cul-de-sacs and courts) that have the U-Turn enabled. According to the Wiki and notes from several Waze Champs, these should be disabled in almost all cases. I could see adding this to the Shift-Z display, or alternatively adding a separate keyboard shortcut dedicated to this task.

Wiki link:  
[https://www.waze.com/wiki/Map\_Editing\_Quick-start\_Guide#U-Turns\_at\_the\_end\_of\_dead-end-streets](https://www.waze.com/wiki/Map_Editing_Quick-start_Guide#U-Turns_at_the_end_of_dead-end-streets)

---

<div class="post-metadata">

### Author: ![AlanOfTheBerg](https://www.waze.com/discuss/user_avatar/www.waze.com/alanoftheberg/32/16350_2.png) [@AlanOfTheBerg](https://www.waze.com/discuss/u/AlanOfTheBerg)
#### Post date: [December 26, 2013, 5:26am UTC](https://www.waze.com/discuss/t/find-dead-ends-with-enabled-u-turns/52824/2 "2013-12-26T05:26:47Z")

</div>

I’d bet one of the community-built tools like WME Color Highlighter could do this.

---

<div class="post-metadata">

### Author: ![pumrum](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/p/FF5252/32.png) [@pumrum](https://www.waze.com/discuss/u/pumrum)
#### Post date: [December 26, 2013, 2:00pm UTC](https://www.waze.com/discuss/t/find-dead-ends-with-enabled-u-turns/52824/3 "2013-12-26T14:00:17Z")

</div>

Many thanks. I hadn’t started to dig through the add-ons in detail, but now that I have I see some tools that are very useful.

For reference, it looks like the WME toolbox will to the trick, though the U-turn highlights are restricted to level 3 so I will have to wait a while before I can work with that feature…

[https://www.waze.com/wiki/Community\_Plugins,\_Extensions\_and\_Tools#WME\_Toolbox](https://www.waze.com/wiki/Community_Plugins,_Extensions_and_Tools#WME_Toolbox)

---

<div class="post-metadata">

### Author: ![gizmouf](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/g/FFC400/32.png) [@gizmouf](https://www.waze.com/discuss/u/gizmouf)
#### Post date: [January 3, 2014, 7:20pm UTC](https://www.waze.com/discuss/t/find-dead-ends-with-enabled-u-turns/52824/4 "2014-01-03T19:20:14Z")

</div>

WME Toolbox won’t show you dead-end segments with U-Turn enabled. Only nodes with at least two segments and U-Turn enabled will be highlighted.

---

<div class="post-metadata">

### Author: ![pumrum](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/p/FF5252/32.png) [@pumrum](https://www.waze.com/discuss/u/pumrum)
#### Post date: [January 5, 2014, 2:48pm UTC](https://www.waze.com/discuss/t/find-dead-ends-with-enabled-u-turns/52824/5 "2014-01-05T14:48:29Z")

</div>

I’ve noticed that. I bumped a feature request in the WME Toolbox forum in hopes that they will add that as an option, since it seems that the champs want all U-Turns in the US to be disabled

---

<div class="post-metadata">

### Author: ![dbraughlr](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/d/FF5252/32.png) [@dbraughlr](https://www.waze.com/discuss/u/dbraughlr)
#### Post date: [January 14, 2014, 4:24am UTC](https://www.waze.com/discuss/t/find-dead-ends-with-enabled-u-turns/52824/6 "2014-01-14T04:24:48Z")

</div>

If this is a rule without exceptions, then it can be applied programmatically. There is no need for humans to find and fix them one-by-one.

---

<div class="post-metadata">

### Author: ![gizmouf](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/g/FFC400/32.png) [@gizmouf](https://www.waze.com/discuss/u/gizmouf)
#### Post date: [January 17, 2014, 1:35pm UTC](https://www.waze.com/discuss/t/find-dead-ends-with-enabled-u-turns/52824/7 "2014-01-17T13:35:28Z")

</div>

Apparently that’s not the case, some exceptions exists.  
U-turn should stay allowed when the end of the cul-de-sac is big enough to easily make a u-turn, and disallowed when it’s a single street.

pumrum \> [WME Validator](https://www.waze.com/forum/viewtopic.php?f=819&t=76488) will show you exactly what you asked for (among other things).

---

<div class="post-metadata">

### Author: ![AndyPoms](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/a/FF5252/32.png) [@AndyPoms](https://www.waze.com/discuss/u/AndyPoms)
#### Post date: [January 17, 2014, 1:40pm UTC](https://www.waze.com/discuss/t/find-dead-ends-with-enabled-u-turns/52824/8 "2014-01-17T13:40:33Z")

</div>

> [@gizmouf](#):
>
> Apparently that’s not the case, some exceptions exists.  
> U-turn should stay allowed when the end of the cul-de-sac is big enough to easily make a u-turn, and disallowed when it’s a single street.

No, they should be denied as well - if they are enabled, Waze will route a user down the street just to make a U-Turn - a direction that should never be given.

---

<div class="post-metadata">

### Author: ![gizmouf](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/g/FFC400/32.png) [@gizmouf](https://www.waze.com/discuss/u/gizmouf)
#### Post date: [January 17, 2014, 2:56pm UTC](https://www.waze.com/discuss/t/find-dead-ends-with-enabled-u-turns/52824/9 "2014-01-17T14:56:18Z")

</div>

That’s what a champ said in the French forum.

If it’s a 100% no go, Waze’s devs should either forbid the possibility to do so or correct that annoying bug (I believe they are already working on it).

---

<div class="post-metadata">

### Author: ![pumrum](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/p/FF5252/32.png) [@pumrum](https://www.waze.com/discuss/u/pumrum)
#### Post date: [January 17, 2014, 3:01pm UTC](https://www.waze.com/discuss/t/find-dead-ends-with-enabled-u-turns/52824/10 "2014-01-17T15:01:39Z")

</div>

> [@gizmouf](#):
>
> pumrum \> [WME Validator](https://www.waze.com/forum/viewtopic.php?f=819&t=76488) will show you exactly what you asked for (among other things).

Yes, yes it will. But the blinking is nearly seizure inducing… When I’m cleaning up U-Turns and RevCons, the WME Toolbox is a much better interface. Turn off satellite and roads, turn on WMET, and you’ll see green and purple triangles where there are U-Turns and RevCons respectively. It’d be great if the U-Turns also included U-Turns at dead ends, since those are the most problematic

---

<div class="post-metadata">

### Author: ![dbraughlr](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/d/FF5252/32.png) [@dbraughlr](https://www.waze.com/discuss/u/dbraughlr)
#### Post date: [January 17, 2014, 4:20pm UTC](https://www.waze.com/discuss/t/find-dead-ends-with-enabled-u-turns/52824/11 "2014-01-17T16:20:49Z")

</div>

I think that a mass update to clean up the whole database is justified. I still do not see the value of having human editors doing mindless work that a simple piece of software could do…

---

<div class="post-metadata">

### Author: ![ply8808](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/p/963EFF/32.png) [@ply8808](https://www.waze.com/discuss/u/ply8808)
#### Post date: [February 16, 2014, 3:35pm UTC](https://www.waze.com/discuss/t/find-dead-ends-with-enabled-u-turns/52824/12 "2014-02-16T15:35:54Z")

</div>

With the validator highlights (update is no longer flashing) and the Junction Node Fixer the tools are now available, but I tend to agree with dbraughlr on an internal fix as some areas are crazy yellow :shock:
