It looks to me like a bad speech to text conversion

txemt wrote:DR EES in AHA in

Change the 'D' to a 'B' break the 'EES' into 'E' and 'S', change both the in's to 'N' and you have "br e s n aha n" which is the spelling of the road.

It looks already correctly spelled I wonder if the driver is complaining about the pronunciation, which of course we have no control over.

sockslabs wrote:

Problem: no break in road

Gimme a break!

Okay, hows this one?

WeeeZer14 wrote:Yeah I think it is usually frustration if it is the same user reporting the same thing over and over again.... "I told you yesterday, this is wrong!" "why is this still not fixed!" "oh come on!"

What txemt said, plus the invitation in every email to come into the editor and take a look at the fix or lack thereof.

shawndoc wrote:

alley is one way. direction is east

Which seems fine on the surface, until you realize the alley in question run almost perfectly North-South.

You're reading the map wrong, it's a really short but very very very very wide street.

ctpoole wrote:I finally have a UR that justifies my posting:

Update Request: Wrong driving direction
Took me to a dead end road. Not destination

And yes, he made the UR at a dead end but there is no indication of where he wanted to really go, so how am I supposed to know?

Mind reading, crystal ball, maybe I close my eyes and pick a place on the map?

Sent from my SPH-D700 using Tapatalk 2

I don't think this is actually a Jolly Driver. Last night I cleared several map problems where the system was complaining that drivers weren't following the suggested routes. The problem is every one of the five such MP's I closed were indicating that Waze had been telling drivers to leave a state hwy (minor hwy type) and turn onto a dead end street. Before closing I skimmed up and down the Hwy in question looking for a bad turn restriction, disconnect or something else that could cause the routing engine to seek an alternate route. But I couldn't find anything.

So this driver may have actually been routed down a dead end road, and the made the report when they realized it was a dead end. My opinion that report is legit, and indicates a minor problem the routing engine might be having.

Aka Bitching Betty with whom military Pilots are so familiar with.

sockslabs wrote:I wonder what the record is for the furthest UR, and fixed.

I found and fixed this in Dover, NH, 85 miles away from the problem it reports:

Bit late to this, but right when I hit CM status, I had a UR in Provo, Utah about how while in Vegas, Waze had refused to route them to Phoenix via US 95. It instead wanted to take them into CA and back on I-10, or back up into Utah and down US 89.

The actual problem was a bad tiger import of 95 roughly 100 miles into AZ on 95.

So, the UR claimed to be about problems in Vegas, about 300 miles from the UR and the actual problem was about 140 miles further on from Vegas.

As to the other more recent posts, loved the one Cheesesteak I've had in Philly and nobody has ever come close to matching it.

Never eaten at Popeye's, but they just opened their first franchises in Utah last year and I just haven't felt like fighting the lines that always surround the one near me.


Tapatalking via my Galaxy S4

bz2012 wrote:I give up!

Update Request: General error
Unmarked yield sign
Submitted 6 days ago

How do I mark a yield sign?

You drive out to the sign with a Sharpie, and mark the darn sign. Just a simple dot will do.

Tapatalking via my Galaxy S4

Tell them, this not a map problem, that there is no way to address such situations. Make sure directionality on the road is correct and close the UR.

Tapatalking via my Galaxy S4

Thortok2000 wrote:Keep in mind we can only view UR's in our editable area.

Keep in mind that many of those most active here are level 5 or 6 and have nationwide editable areas.