Changes to Editor - New Automatic Detected Problem

[mdqueenz]

Seems like something changed in the editor.

There seems to be a new Automatic Detected Problem " Most users did not follow the suggested route".

All of a sudden i have hundreds pop up in my AM area (NYC, Long Island).

Did we know this was coming?

Anyway, no time to waste. Time to start resolving some problems.

MD

[AndyPoms]

Seems like something changed in the editor.

There seems to be a new Automatic Detected Problem " Most users did not follow the suggested route".

All of a sudden i have hundreds pop up in my AM area (NYC, Long Island).

Did we know this was coming?

Anyway, no time to waste. Time to start resolving some problems.

MD

It's been in the beta for a while now... Did not know it was being pushed out to the live editor - and didn't see them in WME when I checked the map at 2am on my way to work...

[mdqueenz]

Sure helps in detecting errors. Picks up on tons of stuff that is incorrect, yet drivers don't ever report it.

MD

[AndyPoms]

Sure helps in detecting errors. Picks up on tons of stuff that is incorrect, yet drivers don't ever report it.

MD

I agree and overall the feedback from the beta was great, there were a handful of bugs that had to be worked out...

[mdqueenz]

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?

[AndyPoms]

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...

[taddison1]

Good concept, but unfortunately it's generating update requests based on old data. For instance, there is a bridge under construction near me and I disconnected its segment 6 weeks ago. Waze now tells me that people are ignoring its directions to go over that bridge, but Waze cannot have been giving those instructions since 6 weeks ago.

Similarly, a lot of the requests I'm seeing are where Waze has suggested a shortcut through a parking lot, which I thought it wasn't supposed to do. The edit dates on the parking lots suggest that perhaps it was only recently changed to Parking Lot Road (I wish we could see more of the edit history details for segments).

So, in many cases the problem isn't identifiable because it was already fixed long ago. In a lot of other cases the routing is technically legal but is one of those cases where Waze suggests something that most people just don't want to do, such as making a right-turn plus a U-turn instead of a left turn.

For these cases where there is obviously nothing useful that can be done, should I mark them as Solved or Unidentified? I've seen other threads where it is suggested that unidentified system-generated requests are thrown to staff editors; On one hand I wouldn't want them to waste time on something that can't be fixed, but on the other hand if they saw some of the routes that are ignored just because users dislike the routing they might be able to give useful feedback to the routing engine developers.

Thanks.

[mdqueenz]

Yes, a lot of the errors have long been corrected, however i have tons where the problem is still existant.

Hopefully once we get past this backlog, the generating of these errors will be much more up to date.

MD

[joshellis625]

sweet baby jesus I have never seen so many SRP's before.

[CBenson]

Good concept, but unfortunately it's generating update requests based on old data.

Yes, this is true. I've seen many that are based on clearly obsolete data. I'm hopeful that once we get the initial round cleared off, then they will be based on more relevant data.