Changes

From Wazeopedia

Junction Style Guide

776 bytes removed, 3 months ago
m
fixed forum link :/ double posted to forum and had deleted link
<!--if the section parameter is defined, do not place the visible banner, only as the code block for the top of a section-->{{GlobalMark/visibleNeedImage}}<!-- #####-----#####-----#####-----#####-----#####-----#####-----#####-----#####----- #### This page has been curated #### #### to be included in the new #### #### Wazeopedia - GLOBAL Wiki. #### #### Please do not make any #### #### edits on this page without #### #### PRIOR CONSENSUS in the Wiki #### #### Updates and Discussions #### #### forum thread for this page. #### #### If a specific forum thread #### #### for this page doesn't exist #### #### please start one. #### #### www.waze.com/forum/ #### #### viewforum.php?f=276 #### #####-----#####-----#####-----#####-----#####-----#####-----#####-----#####--> 
<!--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
| [[File:Jct ramp no geo.png|x100px|border]]
|-
| colspan="3"|[[File:Jct bowtie4waysplitsplit.png|x100pxborder|center|border169x169px]]
|}
The most basic junctions form Basic intersections involve three-way and or four-way intersectionsroad segments meeting at a single point. Some more complex variations resemble bow tiesH or # shapes.
In all cases it is important to configure these intersections properly. Detailed information is covered in the [[Junction Style Guide/Intersections|Intersections]] article.
Make sure that there is a junction indicator (the small blue dot, not just a geometry node) at the very end of the segment. While this one segment does not actually constitute a junction, the small blue dot is a visual indicator to the editor that the end of this segment is properly set up. This is necessary to ensure proper routing out of the segment. See the Cul-de-sac section below on when and how to fix this.
[[File:Jct dead end ex.png|right|border|200px]]
This final junction indicator must be located near the end of the road, but it should be located where there is still pavement as not to negatively impact client routes. Waze only considers the road fully traversed if both ends of the segment are fully crossed. If the junction indicator at the end of the segment happens to be at the edge of the pavement (or off of the road surface if aerials are not exactly aligned), it will be very difficult for a driver to cross that junction. A good rule of thumb is to have the end of the segment the same distance from the end of the pavement as it is from each side of the road.
=== Loops ===
<gallery mode="packed-hover">
File:U-shaped Road.jpg|U-shaped road
File:Jct loop bulb.png|terminal or dead-end loop
==== Every loop must be made up of three or more segments ====
[[File:Loop_3-part_6.jpg|right|150px]]Any loop that does not follow this rule can cause problems for the Waze routing server. If there is no side-street, you must [[Map Editing Quick-start Guide#Splitting a segment|insert an extra junction node]] along the loop. Many new editors will see the extra junction node(s), assume they are not needed, and delete them. Please educate new editors.
====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====
Use of the {{Ramp}} type is governed by the following rules:
* [[Road types/USA]]
* [[At-grade connectors]]
=== Ramp and interchange style ===
For guidance on the proper configuration of ramps, interchanges and wayfinders, see [[Junction Style Guide/InterchangesInterchange]].
== Special Cases ==
Before the current house numbering system came into use, transition nodes were used to aid in house numbering, but that is no longer required.
There may be existing transition nodes on the map for other reasons like remaining after a connecting road is deleted, inherited from to the original base map import when rivers and streams created junctions, etc.
As long as you are '''certain''' it is not a valid transition node, a superfluous junction node may be [[Map Editing Quick-start Guide#Delete a Junction|deleted]]. Doing so will simplify the map, eliminate turn restrictions to maintain, and reduce computing resource needs. Also consider removing the [[Creating and editing road segments#Adjusting road geometry .28nodes.29|geometry node]] which will replace the junction node you delete, if that geometry node is not needed.
A valid use of this technique is at the temporary end of a freeway. As a freeway is built, it is often opened in sections, up to a certain exit. If we map this as a regular freeway segment leading to a ramp segment, no announcement will be made for that final exit, no matter what we name the exit ramp.
This can be confusing if the ramp is set up as a properly signed and numbered exit, especially if a driver is traveling a long distance on this freeway. Imagine traveling down a freeway and seeing your next instruction is "turn left at Main St." You would probably wonder if there was a map error since you shouldn't be making a left turns turn off of a freewaysfreeway.
If we map even just a little of the future path of the freeway, this gives the routing engine a junction which will generate an "exit" instruction at the end of the freeway, thus eliminating any confusion.
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 ===
Since we want to avoid very short segments of road (the GPS chips in consumer devices can be very inaccurate which may make it seem that a driver skipped right over a short segment. This will result in [[Map Problems in Waze Map Editor|automated map errors]] and possible route recalculations in the client,) it may be wise to shift the side roads as far apart from each other as possible with them still in the proper location (along the far curb lines for a residential street for example). This will maximize the length of the short segment between the side roads.
[[Category:Style GuidesGuide]]
[[Category:Table examples]]