Map Problem (MP) In Waze Map Editor

This article covers the automated map Problem reports and appear in the Waze Map Editor as a colored balloon with a white exclamation mark.

Overview

Map Problem is comes from the Waze system when it detects something that is happening in the real world as tracked by the Waze client apps that does not match the logic in the map data. There are two options the editor can use to respond to these Map Problems: Mark as Solved, Mark as Not identified. Just because you do not know the solution doesn't mean that another editor won't figure it out, so do not use Not Identified to mean that you alone cannot identify the problem as this closes the problem for all editors.

Interface Elements

The color of the problem balloon, 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 mark in the icon shows that the problem is open and the color indicates how many drivers have gone through that area with that problem.
A yellow problem balloon has been generated by 1-3 drives.
An orange problem balloon has been generated by 4-7 drives.
A red problem balloon has been generated by 8 or more drives.
The Problem changes to this icon when you "Mark as Not identified". If a Problem is "Mark as Not identified", Waze will not show it again in that location, so "Mark as Not identified" only if you are certain that there is not actually a problem there.
This is a Solved Problem and appears once you fix a problem and "Mark as Solved". Waze will treat this location as "Problem-free". If Waze identifies a new problem in the same place, it will display a new Map Problem there.

When you click on a Problem balloon, the top left 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

Enabling Map Problem Reports

To display the problem reports on the WME screen, use the layer control to turn on the Map Problem layer.

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 and in areas with obstructions to the GPS satellites or cell towers. For parking lot issues, review the guidelines regarding the mapping of 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 as Not identified if there is no actual 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.
If you fix it, Mark as Solved. However, it may be indicated for a time restricted turn or possibly an illegal turn that the driver made anyway; if the turn is restricted in reality, Mark as Not identified.

Driving Direction Mismatch

Drivers are driving against the defined one-way direction of the street. If the road is actually a two-way road, or a one-way road going the other direction, change it and Mark as Solved – and don't forget to enable the correct turns.
However, this could also be triggered by Wazers walking, cycling, or driving the wrong way down a one-way street. If this is the case, do not make any changes, and Mark as Not identified.

Missing Junction

The road segments touch or nearly touch each other, but they are not connected by a junction. If they are connected in fact, then fix it and Mark as Solved.
However, this could also be triggered by GPS inaccuracy. If the route being taken by drivers is illegal or impossible, do not make any changes, and Mark as Not identified.

Cross Roads Junction Missing

The roads intersect each other, however, there is no junction at 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. Fix it and Mark as Solved.
However, sometimes roads that intersect in real life are made not to intersect in Waze if there are no legal turns between them. A user making a turn that is not actually allowed may trigger this Problem in this situation. If this is the case, Mark as Not identified.

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 the route that most users actually took. If you find such a problem, fix it, and Mark as Solved. If there are no missing connections or incorrect turn restrictions, then either leave it open for another editor to review, or Mark as Solved.

Road Type Mismatch

The route goes through some unnavigable roads such as railroad or walking trail. Verify that the road type is actually correct. Under no circumstances should there be a junction between non-drivable segment types like walking trails, runway/taxiway, etc., and other standard drivable segments. If the road type is correct, disconnect it. If the road type is not correct, fix it. Either way, Mark as Solved.

Sharp Turn Detected

Segments are connected by a turn that’s less than 30 degrees.
A "V" shape U-Turn that created from 2 road segments may trigger it, for this situation Mark as Not identified, else correct it and Mark as Solved.

Routing Problem

All turns closed into segment, impossible to route through.
Verify all the legal turn and fix it, then Mark as Solved.

Routing Problem Detected (Unexitable Segment)

Segment does not have an allowed exit point (all turns closed)
Verify all the legal turn and fix it, then Mark as Solved.