Interface Elements
The color of the problem pin, 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 indicates that the problem has been closed.
A yellow problem has has been generated by 1-3 drives.
An orange problem has has been generated by 4-7 drives.
A red problem has has been generated by 8 or more drives.
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.
This is a Solved Problem. 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 Solved.
When you click on an Problem pin, 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.
System detected problem Types
- 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. Please see the guidelines regarding the mapping of Parking Lots. Be advised that more than 60% of this map error type appear to be bogus or require no action be taken at all. Mark it as Solved.
- Restricted turn might be allowed - The route goes through a turn which is marked as not allowed.
- 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.
- Missing junction - The roads are close to each other, however, they are not connected by a junction. This problem can also happen if two roads are close to each other and due to GPS inaccuracy, Waze snaps the driver to one road and then to the other when it "figures out" they really weren't on the other road. In those cases, this problem is bogus. Mark it as Solved.
- Cross roads junction missing - The roads intersect each other, however, there is no junction in the intersection point. This happens most often when a map editor draws a new road crossing an existing one, but forgets to create a junction between the two.
- Suggested route frequently ignored - Waze has calculated that most users did not follow the suggested route. The number in the green circle shows how many drives were taken along that route. Look for missing connections or incorrect turn restrictions which may cause Waze to not choose that driving direction.