# Does anyone have any ideas on this UR?

**URL:** https://www.waze.com/discuss/t/does-anyone-have-any-ideas-on-this-ur/36551
**Category:** Virginia
**Created:** [February 18, 2014, 2:37pm UTC](https://www.waze.com/discuss/t/does-anyone-have-any-ideas-on-this-ur/36551 "2014-02-18T14:37:36Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![n8nagel](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/n/1BAB50/32.png) [@n8nagel](https://www.waze.com/discuss/u/n8nagel)
#### Post date: [February 18, 2014, 2:37pm UTC](https://www.waze.com/discuss/t/does-anyone-have-any-ideas-on-this-ur/36551/1 "2014-02-18T14:37:36Z")

</div>

[https://www.waze.com/editor/?zoom=2&lat=39.07968&lon=-77.56906&layers=2023&env=usa](https://www.waze.com/editor/?zoom=2&lat=39.07968&lon=-77.56906&layers=2023&env=usa)

Problem: incorrect turn indicating left from battlefield to evergreen followed by U turn correct direction should be right turn from Battlefield to Evergreen  
Reported on: February 11

n8nagel(3) on February 17, 2014  
thanks for the report, just to clarify, you were headed west on Battlefield Pkwy and wanted to go north on Evergreen Mill, Waze directed you to turn south and then U-turn? If that’s the case I’m not sure what the problem was as none of the turns are restricted from Battlefield Pkwy and that segment hasn’t been edited since 2012…

Reporter on February 17, 2014  
That’s correct. I’ve seen it happen twice now.

I don’t really know how to address this and to be honest I’m not seeing a problem. Any ideas?

---

<div class="post-metadata">

### Author: ![CBenson](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/c/FD804B/32.png) [@CBenson](https://www.waze.com/discuss/u/CBenson)
#### Post date: [February 18, 2014, 3:46pm UTC](https://www.waze.com/discuss/t/does-anyone-have-any-ideas-on-this-ur/36551/2 "2014-02-18T15:46:03Z")

</div>

I don’t know. I’ve seen a few odd u-turn issues crop up [recently](https://www.waze.com/forum/viewtopic.php?f=8&t=82080) and waze has said there is bug they are working to fix.
