Changes

From Wazeopedia
New balloons
[[Waze Map Editor#Editing Manual |Back to Map Editing]]
[[Image:Problem_pin_highNew_ap_icon_red.png|left]]
''This information here is what is known at this time. Subject to change.''
This article covers the automated map Problem reports and appear in the Waze Map Editor as a colored balloon without a smiley face. Balloons with a smiley face are Waze user reported Update Requests and are covered under [[Update_Requests_in_Waze_Map_Editor|Update requests]].
==Interface Elements==
The color of the problem pinballoon, just like Update Requests, are indicative of something. In the case of Problems, it is the number of drivers affected by, or driving through the problem area, in an unexpected manner. The more drive traces which follow the same route, the higher the likelihood that this problem needs to be fixed. An exclamation point in the icon shows that the problem is open. A check mark and the color indicates how many drivers have gone through that area with that the problem has been closed.
[[Image:Problem_pin_lowNew_ap_icon_yellow.png|left]] A yellow problem balloon has has been generated by 1-3 drives.<br clear="all">[[Image:Problem_pin_mediumNew_ap_icon_orange.png|left]] An orange problem balloon has has been generated by 4-7 drives.<br clear="all">[[Image:Problem_pin_highNew_ap_icon_red.png|left]] A red problem balloon has has been generated by 8 or more drives.<br clear="all">
<br clear="all">
[[Image:Problem_pin_not-identifiedNew_ap_icon_green_not_ident.pngpng‎|left]] The Problem changes to this icon when you mark it as "Not Identified." It is not advised to mark many Problems as Not Identified because this flags the problem to be investigated by other non-local Editors who are not always familiar with local mapping guidelines and may cause more harm than good. <br clear="all">[[Image:Problem_pin_solvedNew_ap_icon_green_solved.png|left]] This is a Solved Problemand appears once you fix a problem and mark it as "Solved". If you see that the problem isn't valid, such as being generated by bad GPS tracks/reception, or is due to bad averaging of GPS track data, mark it Solvedas well.<br clear="all">
<br clear="all">
When you click on an Problem pinballoon, the top portion of the map display area is taken over by the information for the problem.
The top bar of the Problem states that this is an "automatically detected" Problem.
The list below may not be all inclusive of all possible problem types. If you find a problem type not entered below, come to the [http://www.waze.com/forum/viewforum.php?f=276 Wiki Changes forum] to report the missing problem report so it can be added.
As stated earlier, it is generally not advised to mark any of these automated problem reports as Not Identified.
* '''Missing road''' - The roads are too far apart from each other and most likely a road is missing in between. In many cases the missing roads are identified in Parking Lots or and in areas with obstructions to the GPS satellitesor cellular towers. For parking lots lot issues, review the guidelines regarding the mapping of [[Best map editing practice#Parking Lots|Parking Lots]] before continuing. Be advised that a high percentage of this map error type appears to be bogus or requires no action be taken at all. Mark it as Solved if there is no obvious issue.
* '''Restricted turn might be allowed''' - The route goes through a turn which is marked as not allowed. Select the segments around the junction indicated to find if the direction of the turn is limited by a turn restriction. These are usually very accurate in finding incorrect turn restrictions. However, note that in some cases, it may be indicated for a [[Best_map_editing_practice#Time_Restricted_Turns|time restricted turn]] or possibly an illegal turn that the driver made anyway. For both cases either fix it or just mark is Solved.
* '''Driving direction mismatch''' - Drivers are driving against the defined one-way direction of the street. If this is a 2-way segment, change it. Be sure to research whether this is really a 2-way street (or 1-way going the other direction) first, as Wazers walking or biking could be causing the map problem to appear. Once fixed mark it Solved.
9,313

edits