Moderators: support, Unholy, krankyd, The Fej

That link is way too wide to work with... If you can zoom in more it will help.mtnflyr wrote:Most of the errors are occuring in this area.
https://www.waze.com/editor/?zoom=1&lat=37.09684&lon=-122.05364&layers=BFTFFTTTFTTFTTTTFTTTTFT
Not a software update, but a map update (which Waze puts out quite frequently)... Sometimes things like this happen (a risk of using a crowd-sourced map), can they can't be reversed - you just have to find & fix the problem & then wait for the next map tiles update (typically once every week or two right now - look at http://status.waze.com/ for info when updates are put out). Sometimes when mistakes are made, they are caught before they go live by being flagged by automatically generated system detected problems, but not always.mtnflyr wrote:I have been driving in this area for approximately three months with no problems. What could have happened to start the problems? Was there an update to the software for that area? If so could it be reversed?


mtnflyr wrote:This is the last error on my route on CA-17. I see others have reported this same issue on this part of CA-17.
https://www.waze.com/editor/?zoom=7&lat=37.10044&lon=-121.97726&layers=BFTFFTTTFTTFTTTTFTTTTFT

AlanOfTheBerg wrote:Shouldn't this segment be connected across to the CA17 south side? There's turn arrows on the pavement according to aerials. (GPS points are too messy to tell for sure.)
And aside: CA17 doesn't meet the guidelines for splitting around this area.

Return to Website, Community, General
Users browsing this forum: No registered users