Difference between revisions of "External sources"

From Wazeopedia
m (Add elevation changes as a reason for necessary junctions)
m (5 revisions imported)
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<!--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.
+
<!--
-->
+
#####-----#####-----#####-----#####-----#####-----#####-----#####-----#####-----
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.
+
####    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      ####
 +
#####-----#####-----#####-----#####-----#####-----#####-----#####-----#####-->
  
<onlyinclude>* '''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 {{#ifeq: {{PAGENAME}} | Segment length | minimum segment length | [[Segment length|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#Loops|Junction Style Guide on Loops]].
+
Usage of any external copyrighted source of information, in order to add information to the Waze database or maps, is not allowed. External copyright information includes any online or printed map information that is not provided by Waze through the Waze Map Editor interface.
  
* '''Road, city, or state name change'''. There are times when a road, city, or state name will change with no other intersecting road at that point. A junction is added to enable each side of the junction to have a different name.  
+
With the recent acquisition of Waze by Google, Inc., changes have been made to the Waze Map Editor to include updated aerial and street view images from Google. These are considered internal sources and completely acceptable to be used in creating map information for Waze. Google's terms of use restricts use of their map information to specific conditions and Waze has the proper licensing to use what you see inside the Waze Map Editor, but nothing else.
  
* '''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 {{#ifeq: {{PAGENAME}} | Segment length | minimum segment length | [[Segment length|minimum segment length]]}}. This is covered in detail in the [[Junction_Style_Guide#Highway.2FFreeway_Splits|Junction Style Guide]].
+
Using any source of external copyright information puts the Waze maps under danger of being forced to revert all changes done to the map in your area / country.
  
* '''Elevation Change'''. There are times when a road will change [[Elevation#Road_elevation|elevation]] in complex interchanges. A junction is added to enable each side of the junction to have a different elevation.  
+
If any user were to do such a thing, it would taint all the work that person did on the maps and Waze would need to reverse out all those edits. There could also be other adverse effects. Waze has already had to remove all the maps for Chile, and other South American countries because the source of the map data was not properly licensed (not the result of any Waze action).
  
* '''Long segments'''. Segments are best kept under a certain distance. {{#ifeq: {{PAGENAME}} | Segment length |<!-- do nothing--> | See the article [[segment length]] for more information.}}</onlyinclude>
+
Users may negotiate with officials in their country for access to aerial images that Waze can use. The user must be careful not to give the impression that they are acting on behalf of Waze. But as an interested citizen any user can speak with local authority, in a local language, to explain the benefits to their country in making aerial images freely available as a public good.
  
For more information on this topic see [[Unnecessary junctions]].
+
Note that external copyright information does not include any source of information that is provided by Waze through the internal tools of the online editor or application. Also any information developed independently by a user being physically present at a site is acceptable to add to the map as long as it is provided without copyright.

Latest revision as of 10:55, 30 November 2015


Usage of any external copyrighted source of information, in order to add information to the Waze database or maps, is not allowed. External copyright information includes any online or printed map information that is not provided by Waze through the Waze Map Editor interface.

With the recent acquisition of Waze by Google, Inc., changes have been made to the Waze Map Editor to include updated aerial and street view images from Google. These are considered internal sources and completely acceptable to be used in creating map information for Waze. Google's terms of use restricts use of their map information to specific conditions and Waze has the proper licensing to use what you see inside the Waze Map Editor, but nothing else.

Using any source of external copyright information puts the Waze maps under danger of being forced to revert all changes done to the map in your area / country.

If any user were to do such a thing, it would taint all the work that person did on the maps and Waze would need to reverse out all those edits. There could also be other adverse effects. Waze has already had to remove all the maps for Chile, and other South American countries because the source of the map data was not properly licensed (not the result of any Waze action).

Users may negotiate with officials in their country for access to aerial images that Waze can use. The user must be careful not to give the impression that they are acting on behalf of Waze. But as an interested citizen any user can speak with local authority, in a local language, to explain the benefits to their country in making aerial images freely available as a public good.

Note that external copyright information does not include any source of information that is provided by Waze through the internal tools of the online editor or application. Also any information developed independently by a user being physically present at a site is acceptable to add to the map as long as it is provided without copyright.