CBenson wrote:I am reporting the IGN errors that I come across. I fix the error, if I can, at the time I sumbit the report.
that is why i was wondering. if i fix the error the report is a waste of time
* Report it
* Monitor after a few days
* If not fixed, fix it yourself since this error is obviously affecting routing and the Waze experience
gettingthere wrote:In the past we have seen Waze staff (Perlin comes to mind) fixing these eventually. I suppose it comes down to what is more important - bringing IGN mistakes to Waze's attention or fixing the problem quickly so that Waze is functioning properly for the Wazers that are driving in the error of the issue.
i don't thing there is a hardrive in the world with enough memory to handle all the screenshots we need to take to report these errors. now with the 2 week window before updates go live, this might work. but i have this nervous twitch that comes up when i see an error like this. i just want to fix, fix, fix. especially after driving a route on southern and eastern ave in east washington d.c. it directed me onto every side street i crossed, then recalc when i didn't and directed me onto the next, then recalc when i didn't..... waze is not useable in prince george's county. now i admit i will make a mistake or miss something, but it is usually because i am fixing basemap issues on large suburban communities. not a single edit in the middle of a 2 way street.
Area manager in Prince George's County, Maryland. waze 3.0.1 client on iOs 5.0.1