Update Requests (UR) In Waze Map Editor

From Wazeopedia
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 post a message in this forum.

Request pin open-high.pngThis article covers Update Requests submitted by Wazers and they appear in the Waze Map Editor as a colored balloon with a white Waze icon.


An Update Request (UR) is what the Waze client app calls a "Map Issue". When a Wazer submits a map issue for wrong driving instructions, or a disallowed turn, etc., the icon with the small Waze icon is added to the editing map in the Update Requests layer. Due to the Waze terms of service and privacy policy, the username of the Wazer is not displayed. The new communication system added to the map editor enable a 2-way conversation between the Wazer reporting the error and the editor.

When an Update Request is "Mark as Solved" or "Mark as Not identified", an email is sent to the reporting Wazer's registered email address showing the username (not email) of the editor who closed the issue. This secondary communication method enables the reporting Wazer to see the user name of the editor who closed their report, and to make contact in the forums or by private message if they wish.

In the Waze Map Editor, Update Requests contain information about the route the user drove as well as the route Waze had given them. This makes diagnosing the report much easier in many cases, especially for Incorrect Junction and Wrong Driving Directions reports.

When you first click on an Update Request pin, the map will display a window of information at the top of the screen, overlaying part of the map. If you press the show on map button, the screen will recenter and zoom into that Update Request.

WME UR show.jpg

This initial view tries to get you to a spot where you can see the most information. However, you may need to zoom in or out and pan around to see all of the requested route and drive information. In a few cases, the editor may zoom in to a spot somewhat distant from the actual Update Request information, in which case you may need to zoom out far enough so that you can recenter the map manually on the relevant spot.

Note that while this Update Request window is visible, other Update Request and Map Problem icons will appear as faint images until the Close button is pressed.

Interface Elements

The color of the Update Request pin, is the age of the update request. See below for details on the several variations of the Update Request pin:
Request pin open-low.png A yellow update request has been open for 0-5 days.
Request pin open-med.png An orange update request has been open for 6-14 days.
[[File:Request_pin_open-high.png] A red update request has been open for 15 days or longer.
Request pin open conversation-low.png A yellow update request has been open for 0-5 days and has a conversation in progress.
Request pin open conversation-med.png An orange update request has been open for 6-14 days and has a conversation in progress.
Request pin open conversation-high.png A red update request has been open for 15 days or longer and has a conversation in progress.


The Update Request changes to this icon when you mark an Update Request as "Not Identified" because you cannot locate a reason for the request or the request is unclear. Not identified update requests are visible on the map for up to seven (7) days after closure.


This is a Solved Update Request which has a conversation. Solved update requests are visible on the map for up to seven (7) days after closure.

When you click on an Update Request pin, the top portion of the map display area is taken over by the information for the update request.

Meta Info


In the top left of the screen you will see the problem description from the user (if entered) and when the user reported it.

Display Related

Show On Map

WME Update ShowOnMap.JPG At the right of the "Map Problem" display will include this hyperlink that will recenter and zoom the display into the area covering the Update Request. The display can also be manually zoomed and panned to the area.

See In Street View

WME Update StreetView.JPG At the right of the "Map Problem" display (beside the "Show on map" button) will include this hyperlink that will open a street view window that will cover the half right of the map in Waze Map Editor which showing the surrounding of Update Request. With the help from the street view, some Update Request can be solved without further communication with the requester.

Drive And Route


On the right will be zero, one, or two checkboxes, depending on the data Waze was able to capture from the app. Each one enables you to show the Route which Waze requested the user take, the user's actual drive, or both. Note that due to privacy concerns, the route driven will only be about 160m (probably longer) in length, and will not include the very beginning or end of the user's drive. This may make it difficult to truly understand where the user actually ended up driving if there are a number of intersections past the end of the route indicator.

Report As


At the bottom of the Update Request area is where you can take an action on the update request. You can leave it open, or Mark as Solved or Mark as Not identified. This action, once you Save it, marks the Update Request as closed in the system, and neither you nor anyone else will be able to change the status again.

Closed Update Requests are visible on the map for up to seven (7) days after the closed date using the green icon. Comments added after the closed date will reset the closed date and extend the visibility of the UR.

Mark as Solved

If you are able to identify a reason for the reported issue, and if you are able to fix the problem in the editor, fix the problem and save your changes. Then mark the update request as Solved.

Mark as Not identified

For various reasons, such as lack of detail provided by the Wazer, or conflicting route vs. drive trace information, you may not be able to identify the source of the reported problem. In these cases, you should attempt to initiate a conversation with the reporter.

If a conversation has already been initiated by another editor and a reasonable time has passed since last hearing from the reporter, suggest that it be closed. Wait for that editor to contribute prior to taking further action.

If you do not receive a response within a reasonable period of time (minimum 3 day) after asking the question, you may consider close the Update Request by Mark as Not identified.

Also, users may sometimes report problems that are valid problems, but not problems that can be fixed in the editor – for example, problems with the app not loading map tiles properly. These should also be Mark as Not identified, with an explanation to the reporter that the reported issue cannot be fixed in the editor.

Before Saving

Before Saving, enter a comment about why the request is being reported/closed in the manner you have chosen and Send that comment before clicking Save.

Once you choose one of these selections, you need to click the Save button to save your changes. As soon as you click Save, any Update Requests and map edits you updated since the last save will be saved, and an email is sent to the Wazer who submitted the update request.

Next Update Request

By clicking on the Next update request button at the bottom of the Update Requests will direct us to next Update Requests.
When encounter an Update Request that been handle by other editor and the communication between the editor and requester is still on going, you can click the Next update request without interrupting the conversation.


At the top right of the Update Request information area is a Close button X Button.JPG. This button doesn't actually mark the Update Request as closed but simply dismisses the interface for reviewing the update request. It also hides the route information displaying on the map. This button is useful for clearing up the map display area while you work on solving the Update Request. Click on the Update Request again to bring up the details so you can mark the Update Request as Solved or Not Identified.

Driven And Requested Routes

The route that the user received from Waze will be shown in purple, just like in the app. The route that the user actually drove is in bright green.

If you cannot see the direction arrows or direction of the route, you may need to zoom in. Once zoomed in, the lines will show the direction of travel.

WME Update Request Zoom Detail.JPG

One of the following turn instructions is placed at each junction on the purple request route line:

  • Big direction forward.png - Continue straight/forward
  • Big direction right.png - Turn right
  • Big direction left.png - Turn left
  • Big direction exit right.png - Exit/Keep right
  • Big direction exit left.png - Exit/Keep left
  • Big directions roundabout.png - Roundabout numbered exit turn
  • Big directions roundabout l.png - Roundabout left turn (this instruction has been replaced by Roundabout numbered exit turn instruction)
  • Big directions roundabout r.png - Roundabout right turn (this instruction has been replaced by Roundabout numbered exit turn instruction)
  • Big directions roundabout s.png - Roundabout straight through (this instruction has been replaced by Roundabout numbered exit turn instruction)
  • Big directions roundabout u.png - Roundabout "u-turn" (this instruction has been replaced by Roundabout numbered exit turn instruction)
  • Blank Arrow - junction error (see below)


Route Diagnosis

Using the information provided by any divergence of the requested route and user drive, you can look for turns which may need to be allowed at intersections.

If you are able to determine a fix for the user's report, you may click the "Mark as Solved" button and then click Save.

There will be times when the user description for the problem is provided, but does not seem to relate to the portion of their route you see on the map. This typically happens when the driver initially looks at their overall route and they see a problem at the end of the navigation turn list or on the map. They mark the problem there at the beginning of their trip, but don't realize an editor only sees about a mile of their route and nothing else about their trip. There is nothing you can do in these cases if they did not provide enough information to identify the problem area without the map route visual so "Mark as Not identified" for these Update Request. The original reporter of the problem may then reply directly to you or come to the forums to better explain what they saw.

Turns Diagnosis


Big direction left.png When reviewing the route, it is easy to be confused by the black turn direction arrows displayed at junctions along the Waze recommended route. Note that these will display the turn for the direction being traveled. Because the Waze Map Editor uses north-up orientation, for a route going south, these turn arrows will appear to be backwards. You need to put yourself in the orientation of the driver. Details are covered in the Driven and Requested Routes section above.

Blank Arrow

There are circumstances which will cause Waze Map Editor to show a blank turn arrow tile at a junction.
The blank instruction means the routing server failed to provide an instruction in this node. The client treats this as a non-audible continue straight instruction, which usually means the instruction the user hears and refers to is the next instruction after the blank one.

The reasons for this are:

  1. There is something invalid with the junction
    • It could have a short circular segment
    • Very distorted in some way
  2. There is a bug in the routing server when handling this node.

If the reason is #1, it should be quite obvious and fixable in the editor. If not, it may be #2, in which case you will need to open a support ticket.



Two-way communication with the user who submitted a Map Issue (the Reporter) from the App is possible via a feature called Conversations. Newly submitted Update Requests will have no replies and so the Conversations button will show "0" until replies are added. The Conversation feature allows editors to ask for clarification of the Reporter, and allows the Reporter to respond back. This conversation can go on until the issue is clarified and resolved or determined to not be solvable.

Note :
You will need to have Update Requests checked in the Map Layers to view open conversations.



To the right is an example of a conversation with several replies from both an Editor and the Reporter. The conversation button will show the total number of replies or comments which have been submitted by Editors and the Reporter for that Update Request.

The Reporter's comments are shown in white/gray bands and the Editors are shown in white bands. The colors alternate between white/gray and white if the Editor or Reporter enters more than one comment before the other person responds.

Note :
If you comment on your own Update Request (you opened it as a Map Issue in the app), you will show as the Reporter in the conversation thread.


To open an Update Request conversation, click the Conversation button. The Conversation button alternately opens and closes the Conversation panel. Collapsing the Conversation panel allows you to see more of the map.

Add a comment or question into the box marked Enter comment. To submit the new comment, click the Send button. You may enter as many comments as you like.

When you enter a comment, the system will automatically set you to Follow the Update Request conversation. You may click the Unfollow button if you do not wish to be notified of replies. See the Notifications section below for details.

Once a comment is entered, it cannot be removed from the Update Request Conversation. Your comments will be visible to all editors.

You may elect to receive notification of comments and replies on an Update Request by check the Follow conversation. You can do this on any Update Request on the map. Uncheck the Follow conversation to stop receiving reply notifications.

Any Editors who are Following an Update Request can also add comments from the Waze App Inbox message they receive after any reply is added to the Conversation.

It is likely that you will find the drive and route data to be very helpful in resolving Update Requests without needing to request additional information from the Wazer who submitted the Map Issue.


Here is a quick summary of notifications which the system sends:

  • If you are the Reporter
  1. You will receive an email to your registered email address (if you have one) and a message in the Waze App Inbox when another Editor adds a comment to the UR Conversation
  2. You will receive an email and a message in the Waze App Inbox when an Editor (who is not you; see note below) closes (marks Solved or Not Identified) the Update Request
  • If you are Following an Update Request Conversation (as an Editor)
  1. You will receive an email and a message in the Waze App Inbox when either another editor or the Reporter adds a comment to the Conversation
  2. You will receive an email and a message in the Waze App Inbox when an Editor other than you closes (marks Solved or Not Identified) the Update Request

The Resolution Process / Etiquette

When you respond to user reports, you are interacting with the original reporter, and you may also be interacting with other Waze map editors who respond to the same request. The recommendations in this section are designed to:

  • Promote harmony between editors and the reporter, and improve the good reputation of Waze and its user community
  • Promote harmony among editors and prevent conflict or duplication of effort
  • Engage the reporter productively, efficiently, and courteously in the problem resolution process

Below is a description of the issues that require finesse in your response etiquette to prevent or resolve.

Missing Information