Necessary junctions: Difference between revisions View history

(simplify language on name and elevation changes.)
(Marked as global wiki page)
Line 1: Line 1:
<!--if the section parameter is defined, do not place the visible banner, only as the code block for the top of a section-->{{GlobalMark/visible}}
<!--
#####-----#####-----#####-----#####-----#####-----#####-----#####-----#####-----
####    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      ####
#####-----#####-----#####-----#####-----#####-----#####-----#####-----#####-->
<!--This page is translcuded into other pages and is generally not expected to be viewed by readers on its own. However it does include basic information to prevent confusion for an otherwise unexplained list of bullets. The "onlyinclude" functions will only transclude that content into other pages requiring the list itself. The special "ifeq" template prevents hyperlinks to the same page into which it may be transcluded. All other pages would include the hyperlinks.
<!--This page is translcuded into other pages and is generally not expected to be viewed by readers on its own. However it does include basic information to prevent confusion for an otherwise unexplained list of bullets. The "onlyinclude" functions will only transclude that content into other pages requiring the list itself. The special "ifeq" template prevents hyperlinks to the same page into which it may be transcluded. All other pages would include the hyperlinks.
-->
-->

Revision as of 12:56, 1 July 2015

Junctions with three or more connected segments are necessary if the segments themselves are supposed to intersect for routing purposes. Generally speaking, most two-segment junctions are not required, however some of them are required to ensure the best operation of Waze. The list below includes examples where a two-segment junction is necessary and should NOT be removed.

  • Loop roads. A single segment cannot loop back upon itself, so a junction is required to create two separate segments. It does not matter where the junction is located, so long as each segment meets the minimum segment length. Some roads have two separate segments that share the same start and end junctions creating two alternate paths between them. These configurations cause routing problems and require one of the two segments to have a 2-segment junction. More details are covered in Junction Style Guide on Loops.
  • Road, city, or state name change. When the road, city, or state name will change between intersections, add a junction so the segments on either side may have a different name.
  • Elevation Change. When elevation changes at complex interchanges, a junction can be added to introduce an elevation change.
  • Ramp or freeway splits. There are cases where a freeway may split into two separate freeways. In order to provide navigation to drivers, it may be necessary to create short segments on the freeway to show the two different road names at the split. Under certain situations it may be best to make the segments as short as possible, so long as each segment meets the minimum segment length. This is covered in detail in the Junction Style Guide.
  • Long segments. Segments are best kept under a certain distance. See the article segment length for more information.

For more information on this topic see Unnecessary junctions.