Changes

From Wazeopedia

Junction Style Guide

41 bytes added, 3 months ago
m
fixed forum link :/ double posted to forum and had deleted link
<!--Editorial Reminders--><!--To Do - U-Turn Solutions for "Road not connected" error -->
{{construction
| contact = httphttps://www.waze.com/forum/viewtopic.php?f=2761636&t=86666283510
| contacttype = forum
| draft = no
=== Loops ===
<gallery mode="packed-hover">
File:U-shaped Road.jpg|U-shaped road
File:Jct loop bulb.png|terminal or dead-end loop
====Two-segment loops====
Two-segment loops create a situation called "same endpoint drivable segments" or "same connection segments". There are two or more ways to get from one junction node to another without going through any other nodes. They can cause a problem for the Waze app regardless of the direction, or other attributes of the segments. This is because the routing server gives your mobile app a list of node idsIDs only, but the app needs to tell you which segments to drive on. If there are two ways to get from one node to the next without going through any other nodes, then the Waze app might just have to guess. It might guess a detour off the highway through a gas station service road or scenic overlook. Please save Waze from this silliness. Correct two-segment loops.
====One-segment loops====
Conversely, if we do NOT want an exit instruction at the end of a freeway, ensure there are no road segments extending past the final exit, to ensure the final exit is the only path out of the final freeway segment.
 
==== Fake ====
''(coming soon)''
=== Offset Roads ===