I am having major issues with directions for Waze - I live/work in Fairfax Co, VA, but drive into Washington DC a lot. I basically cannot use Waze for GPS directions because Waze cannot handle all the weird one way/HOV only roads around here and I have no idea how to correct it.
For example, a major highway - Rock Creek Parkway - goes through the city in one direction 2 x during the day, and both ways the rest of the time. Part of the road is also closed to all traffic on the weekends. RCP is awesome for traffic avoidance as long as you get it going the right direction.
Other examples:
- 66 within the beltway is also HOV 2 only during rush hour. Outside the beltway, it is not HOV only.
- Parts of 15th and 17th streets in downtown DC that are one way during rush hour.
- Canal Road in DC/MD.
For example, this morning at 8am, Waze told me to take 66 (HOV only until 9am) to Rock Creek Parkway (one way the opposite direction I was going). Because I know better, I avoided those roads, but I know that someone unfamiliar with either road would end up being very very stuck (if you try to get on RCP during rush hour, you are trapped into a horrible loop of twisty/turny roads with minimal signage and since Waze keeps trying to direct you onto RCP, it cannot help you get out of it).
Please read the FAQ per the forum rules, and search the forum. “Rock creek parkway” will probably result in a few dozen hits.
As Alan indicates this has been raised many times.
There’s not much to say other than yes we know (although I had thought that 15th and 17th no longer reversed). Waze keeps telling us that we will be able to implement time based restrictions soon. The ability to handle HOV restrictions seems also to be in works although I won’t hazard a guess as to when that would be implemented.
I’ve moved this to the DC forum as I’m interested in whether 15th and 17th really do still reverse.
Speaking on this topic - how are people handling UP’s for people complaining about 66, Rock Creek etc?
Like I’m fairly certain both of these are due to time of day restrictions:
https://www.waze.com/editor/?zoom=6&lat=38.90277&lon=-77.05773&layers=BFTFFTTTTTTTTTTTTTTTTTFTT
BTW any word when this will be implemented?
Back in the cartouche days I had the standard response informing the users that waze does not yet provide for time based restrictions and that they could express their need for the feature in uservoice. With the coming conversations in WME, we will again be able to tell users that waze does not yet provide for time based restrictions.
Its said it will be implemented soon. But I might actually believe that soon means months not years now.
For now are you marking them as resolved or Not Identified?
I can’t bring myself to mark them solved.
Makes sense - which is why I asked. For now I’ll ignore these until I have access to the WME beta or the stable version allows for communication to the user. Shame there is no “Known Problem” option haha.