Main Page/Problem reports History

This new page is currently undergoing modifications. The information presented should be considered a draft, not yet ready for use. Content is being prepared by one or more users. Do not make any changes before you send a private message to [Dude495 this user].

Problem Reports

In the Waze Map Editor we can see two different kind of Problem Reports:

Request pin open-low.pngRequest pin open-med.png URs (Update Requests; map problems reported by Waze users)
Problem pin open-high.pngProblem pin solved.png MPs (automatically generated Map Problems)

They show where the map needs work. We must solve them to fix the map. URs also give us a way to contact our fellow Wazers, who may become interested in editing.

Other reports on the map are Wme placemarker new.png Place Update Requests (PURs), which are treated on the page about Places.

Update Requests (URs)

Request pin open-high.pngRequest pin open-med.pngRequest pin open-low.pngRequest pin solved conversation.png

Update Requests are shown as balloons with a blank Waze icon. Depending on their age, they are colored from yellow (fresh) to red (old). Green URs are closed by an editor. In well managed areas, URs are handled quickly. It gives the best opportunity to get local knowledge from the reporter to help you fix the map.

Suggested time-table:

  • First response within 7 days (preferably quicker!)
  • If no reaction from the reporter, send a reminder after 7 days
  • If no reaction to the reminder, close the report after another 7 days

Guideline for handling URs

start a conversation. Be aware that the reporter probably is not an editor.
  • Respond to URs in (Roman) Urdu and/or English
  • You may use this list of responses to common UR problems to help you.
  • UR reporters are our partners in fixing the map. Always use friendly comments that show our appreciation. Ask for information in a friendly way, thank them for working with you, and always leave a comment before closing.
  • Officially, nobody ´owns´ a UR. However, if another editor is already working on a UR, it is polite to get in contact with him or her. You may find a solution together. If the editor does not react within two weeks after the initial response, you handle the UR as described below.
  • Some problems are easy. Some problems are difficult. Sometimes the reporter gives incorrect information. You can always ask a more experienced editor for help solving a UR.
  • Sometimes a higher Level editor is needed to solve the problem, because the involved segments are locked at a higher Level than your own. Check the level of the segments and those that are connected to it, before you start editing. In case of a higher lock, request an unlock in the forum or in slack, or assistance from a higher level editor.


  • If the report has enough information, please fix the problem.
-Tell them what you did.
-Say "thank you". Maybe they will send more helpful reports after this.
-After it is fixed, close the UR as Solved.
-Remember to send a closing comment.
  • If you need more information, ask.
-Be friendly, say thank you, and send.
-Look at the provided standard responses for examples.
  • If the reporter did not answer after 7 days, send a reminder message.
It often happens reporters do respond only after a reminder.
  • If the reporter does not respond to the reminder after 7 days, check again.
-Try to solve the problem.
-Check other URs in the neighbourhood for more information.
-Update the map at that location where possible.
-Ask your fellow editors for help.
  • Close the UR as Solved only if you really solved the problem in the map.
  • If you did not solve a map problem, do NOT mark the UR Solved:
-If the problem is with the app, give the reporter a link to the Waze support pages.
-If you did everything to handle the problem, but it can't be solved in the map, you can close it as Not Identified.
-Use a closing comment like the provided default response.
-Remember to send the comment.

Older Reports

Many areas are still not maintained well, and we have very old Update Requests open. The URs may signal where we have to work. Also, it provides a possibility to get into contact with our users.

  • Use your best judgement as how to handle them.
  • You may follow the guidelines above, and use the default response asking for more info.
  • Do include an excuse for responding late.
  • Again, always try to improve the area before closing the UR.

Elaborate information on URs can be read in the global page about Update Requests. Be aware, that if guidelines differ from what is written above, the Pakistan guidelines prevail. Once you are experienced handling URs, you can use the script URC to facilitate it.

Map Problems (MPs)

Problem pin open-high.pngProblem pin open-med.pngProblem pin open-low.pngProblem pin solved.png

Problem reports are automatically generated reports, that appear in the Waze Map Editor as a colored balloon with an exclamation (!) mark. Balloons with the Waze silhouette are user reported Update Requests and are covered in the paragraph above.

Map Problem Missing road.png

  • There are several kinds of MPs. In base map areas, you will find Missing road, Crooked segment detected and Restricted turn might be allowed most often.
  • Other kinds of MPs are described in the Global Page on Map Problems.
  • Try to solve the problem and close the MP as Solved.
  • If you are sure it is not a map problem, close it as Not Identified'
  • If you don't know how to solve it, please discuss it with your fellow editors first before closing it as Not identified.

Elaborate information on MPs can be read in the global page about Map Problems. Be aware, that if guidelines differ from what is written above, the Pakistan guidelines prevail.