https://www.waze.com/wiki/At-Grade_Conn ... _mapped.3F
To remove the bolded section:
Should the connector be mapped?
First and foremost, the need to have the connector mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes.
There are only a few situations in which connectors are called for in an intersection:
When the turn lane physically separates from the main road well in advance of the intersection
When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation
When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier
When there are user complaints (update requests) that the audible was too late, or that the map should have shown a connector
When you get an automated report (map problem) that the roads are too far apart due to the intersection being too far from the turn lane
As written, we'd be adding turn lanes to just about any decently sized intersection that uses a mapcat bowtie. I feel the rest of the reasons listed for adding a turn lane cover the times when a turn lane is needed. The MPs about roads being too far apart have too many false positives to be used as a justification by itself to add a turn lane.
Inspired by this thread:
[EDIT: Wiki change completed Nov 18, 2013]