The new Waze Wiki, aka Wazeopedia, is now live at Wazeopedia.waze.com! While this legacy wiki will remain accessible for the time being, it is no longer updated by the community. For the most up-to-date guidance, please visit your local Wazeopedia.

Please do not make any more updates to these legacy wiki pages, all future updates should be made in your country's local Wazeopedia.

Clock over a larger globe

Difference between revisions of "Junction Style Guide"

From waze
Jump to: navigation, search
(The Basics)
(The Basics)
Line 34: Line 34:
  
 
[[Image:Jct_4_45_curve.png]]
 
[[Image:Jct_4_45_curve.png]]
 +
 +
The above image is what you would see zoomed in as close as possible.  Zoomed back out, it looks just like the image showing the junction without any geometry nodes.

Revision as of 18:45, 1 August 2012

Simple is better

When representing junctions between roads, we sometimes have to blur the lines between the physical and logical worlds. The primary goal should be to represent things as simply as possible and only introduce complexity to deal with an issue.


The Basics

Lets start with the very basic case of one road branching off from another. Most of the time they will probably meet at close to a 90 degree angle. This is the simplest situation to deal with since the physical and logical versions of the roads match up very well.

Jct 3 90.png

But you will probably find roads that meet at odd angles as well. Even in urban areas with rigid grids, you will often find at least one road that has existed since prior to the establishment of the grid which cuts through town at strange angles. The initial urge will be to represent the junction as it is in the physical world - two lines running into each other at some angle.

Jct 3 45.png

But there are issues with this method. Depending on the angles, the client may give a "Keep Right" instruction to the driver when a "Turn Right" instruction is more appropriate. In some cases, it is even possible the angle may be such that no instruction is given at all. Or worse yet, the routing engine may determine that it isn't possible to make a very sharp angle and not suggest a turn (in the example image, headed south and then turning left to head east).

To eliminate ambiguity, we need to treat the junction from a logical point of view. Since we want to be given basic "Turn Left" and "Turn Right" instructions, we have to treat it like it was a basic 90 degree intersection. But how do we do that when the roads don't actually diverge at 90 degrees? What we need to do is to add some geometry nodes to make the branch road leave the main road at close to 90 degrees, then we gradually curve to match the true departure angle.

Jct 3 45 curve.png

Now we have a junction that logically works like a basic 90 degree junction but it also fits the reality of the physical world.

We can easily scale the above approaches to a four way junction. Again we can expect to mostly see angles close to 90 degrees.

Jct 4 90.png

And if we have that odd street cutting across town at an odd angle, we again want to avoid the odd angle at the junction...

Jct 4 45.png

...and we want to use geometry nodes to bring the actual junction to 90 degrees. You can zoom in as close as you can and add a single geometry node on each side. This will give us the proper angle but make it virtually invisible to users so it looks just like the physical world.

Jct 4 45 curve.png

The above image is what you would see zoomed in as close as possible. Zoomed back out, it looks just like the image showing the junction without any geometry nodes.