AlanOfTheBerg wrote:If Wazers continually get stuck in the back-ups waiting a long time to make a difficult turn, then Waze will eventually have that data and be less likely to give that turn instruction at the times of day where it finds traversing that segment-to-segment pair is very slow. I say let the data do the work.

There's still the uncertainty of whether the node transit time is learned only if the transit happens. If the turn is never taken during the difficult high-traffic times, it may never collect the data needed as what happens when it doesn't have data for that ToD slot but it does for other times of the day?

This is something we should bring up at the next meet if it isn't answered clearly enough before then.

sockslabs wrote:The following sequence seems to unwedge the save button:

Click on the report.

Hit Solved.

Hit Close.

Click on the report again.

Hit Not identified, and the save button wakes up.

My trick was to click Solved then change one other item (change a turn, move a segment, etc.). This would enable the save and undo buttons (number of changes would be off by one). I would then undo the last change (now the number of changes is correct) and then save.

kentsmith9 wrote:How about this one? It came up as "Most users did not follow the suggested route"The roads being proposed as the route are dead ends. They are unnamed and have no city, so there is no address for which to navigate. I did notice they are all recently edited by staff in the last week and these would classically be Portola Valley roads, so maybe there is some connection between them causing this as a false route problem.

That type started several months ago & is discussed in several places in the forum... It works better in urban areas than rural ones...

Several things to note about that type of MP1) The initial run used very old data, so many of them had been solved before they started showing up on the map2) A lot of the ones on dead ends are actually Waze turning the user around and sending them back where they came, the tracks are perfectly overlapped, so you can't see the one of the paths.3) Check both routes (and continue on the one the users took for a while) for screwy turn restrictions/soft turns/one-way roads that should be the other way/one-way roads that should be two-way or vice versa

mdqueenz wrote:What does the number in the bubble represent (in the driver's actual route)? Is it the number of times that instruction has been ignored?

The number of drivers that went that way - sometimes you will get two (or more) green lines that didn't follow the instructions but went different ways... For example, Waze said "turn left", 8 drivers went straight & 3 turned right...

bgodette wrote:There's still the uncertainty of whether the node transit time is learned only if the transit happens. If the turn is never taken during the difficult high-traffic times, it may never collect the data needed as what happens when it doesn't have data for that ToD slot but it does for other times of the day?

This is something we should bring up at the next meet if it isn't answered clearly enough before then.

I agree that if no one takes it, it can't get the data, which is why I often recommend taking that obnoxious route a few times and let Waze gather the data.

CrackedLCD wrote:Is this feature only in certain areas so far? I zoomed out just a little while ago and didn't see any new errors beyond the existing ones on locked roads that I cannot fix and are leaving for Level 5s in the area to handle.

I find it hard to believe we're totally error free in my region, but it would kinda awesome if it were true. There's some hard working editors around here who've really made these roads shine over the last six months or so.

The error is going to be prevalent in high-traffic areas due to statistical reasons. The same goes for almost all problems and update requests. Where there is more Wazer density there will be more update requests and problems.