One thing to remember when looking at MPs of the type "Suggested route frequently ignored" / "Most users did not follow the suggested route" is that for some reason many of these seem to be generated by quite outdated drive and routing data, where the problem has been solved conclusively, but the Waze automated map problem routines keep putting them on the map over and over. I see these SO frequently, and yet so rarely do I see an actual user submitted map problem where Waze proposed a route over a parking lot road. In the cases where I do see such URs, I suspect that the situation is often what jemay has suggested, that we can't see the route end point in the UR, and that Waze didn't actually route PAST the parking lot or private road, but merely chose it because the destination address marker was closer to the alley than to the street segment.
There has been some debate about whether Waze is still using old data for these MPs, or if indeed people are still being routed over parking lot road segments. I submit the following exhibits as evidence that such MPs are still being generated after the problems have been solved. In this case, the modification dates of the disconnected segments were well over a month earlier than the date when I found this MP and captured the screenshots (March 9 / April 20). It's interesting to me that the Waze suggested route is broken approximately where the segments are disconnected. It's as if the automated process knows that the problem has been solved, but it can't talk to itself...
I've been following this issue as it pops up in thread after thread, and I'd really appreciate a PM if any of you editors out there find examples of actual user submitted map errors where its clear that Waze has routed through a parking lot road or private road segment which is not at the end point of a route. Only with URs can we verify that the routing occurred after a segment road type has been set.
Area Manager - Southern California / Country Manager - United States