sockslabs wrote:Reported on I-290W: Turn not allowedsockslabs(3) on June 24, 2014
What you you mean 'turn not allowed' on 290 W?Reporter on June 24, 2014
No U turn ..sockslabs(3) on June 24, 2014
I don't understand. You're on 290W, a 3-lane interstate highway. Taking a U-turn is going to kill somebody. What do you mean?
He hasn't responded back -- I fear something terrible may have happened.
xteejx wrote:Oh God please don't mention the messed up timings for TTS!
In regards to the General Error UR option... I wonder if it could be something to bring up with Waze directly at the UK meet up this Saturday. I want to push for a report cache option anyway for low signal areas. Maybe not for traffic but for user reports and map errors it'd be helpful.
Also maybe a way to record a Wazers voice (so much easier) recording of the issue which we could then playback in WME.
Sent from my GT-I9505 using Tapatalk
sockslabs wrote:qwaletee wrote:
Ummm, commenting without context, but isn't that his exact complaint? That Waze is suggesting a U-turn on the highway?
Waze never suggests U-turns. Instead it'll send you 2 miles down back roads and take 3 lefts. Plus the interstate segments are all 1-way. So: huh?
jasonh300 wrote:sketch wrote:Hmmmm, although isn't it true that the Shell and Chevron logos are typically in title case, whereas "TEXACO" is generally in all caps?
SHELL and TEXACO are all caps on their signs but Chevron is mixed case. I convert everything to mixed case in the editor so as not to be obnoxious. However, I haven't figures out a way to make the double x in Exxon in the editor.
Jay91150 wrote:Reply should have just been "New Jersey."
So we're branching out from solving map issues now?
Users browsing this forum: Bing [Bot]