Nope, understood!
I want to bring up the "Simple is better" text:
Related but distinct, I think the "intersections" page will need a brief explanation as to when to include turn lanes and when not to, with a link to the at-grade connectors page. There doesn't seem to be any mention of them at all except in the example on "controlling turn instructions".
I want to bring up the "Simple is better" text:
While this isn't necessarily bad, our number one goal should be accurate and non-misleading navigation instructions. Simplicity is fine, but not at the expense of navigation. Something with a tone like "Keep the map as simple as possible without sacrificing accuracy of navigation instructions."When representing junctions, intersections, interchanges, cross roads, corners, etc., the Waze map does not need to perfectly match the road layouts it represents. The primary goal is to represent the real world as simply as possible in the maps and only introduce complexity in the maps to address complex issues.
Related but distinct, I think the "intersections" page will need a brief explanation as to when to include turn lanes and when not to, with a link to the at-grade connectors page. There doesn't seem to be any mention of them at all except in the example on "controlling turn instructions".
Re: [Page Update] Junction Style Guide