Update Requests
This information here is what is known at this time. Subject to change.
Update Requests are visible and contain useful information in the Waze Map Editor. Since the proposed two-way communication system with the end user is not built yet, the Update Requests layer in the Waze Map Editor currently does not inform the Wazer who submitted the Map Issue that their Update Request was closed.
Overview
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 display will automatically center on the pin and zoom in to an appropriate level.
This initial view tries to get you to a spot where you can see the most information. However, it is likely that you may need to zoom in or out and pan around to see all of the requested route and drive information.
Interface Elements
The color of the Update Request pin, just like Map Problems, are indicative of something. In the case of Update Requests, it is the age of the update request. An exclamation point in the icon shows that the update request is open. A check mark indicates that the update request has been closed.
A yellow update request has been open for 0-x days.
An orange update request has been open for x-y days.
A red update request has been open for more than y days.
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.
This is a Solved Update Request.
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.
The top bar of the Update Request states that this is a User Reported Problem.
Meta Info
To the left you will see the type of report, a description if the wazer entered any text information to explain the issue, the date of the report and the username of the wazer.
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 is to allow you to select whether to show the Route which Waze requested the user take, the users actual Drive, or both.
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 it as Solved or Not Identified.
If you are able to identify a reason for the reported issue, fix the problem and save your changes. Then mark the update request as Solved. 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 mark the Update Request as Not Identified.
Once you make once of these selections, you need to click the Save button to save your changes.
Close
Way to the right of the Update Request information area is Close button. This closes the update request in the Waze Map Editor. Keep in mind that the Update Request database in the Waze Map Editor and Cartouche_old are two independent databases. Prior to January 25, 2012, Update Requests will be duplicated and need to be dealt with in each editor.
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. Additionally, at each junction on the requested route (purple), a turn marker will be shown.
One of the following turn instructions is placed at each junction on the purple request route line:
- Continue straight/forward (client doesn't give this instruction by design)
- Turn right
- Turn left
- Exit/Keep right
- Exit/Keep left- Blank Arrow - junction error (see below)
Diagnosis
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.
In beta testing of this feature, it was noticed that Waze often routed users either against turn restrictions, or in odd, non-optimal routes. Through communication with the drivers, it was determined that most of the Wrong Driving Directions reports were due to the "Prefer Goodie Munching" or "Prefer Cookie Munching" option being enabled in the app. This is the reason why it is now recommended that this option be turned off and that Waze is looking to remove this feature completely.
If you are able to determine a fix for the user's report, you may click the Solved action on the Report As section and then click Save.
Turns Diagnosis
Orientation
When reviewing the route, it is easy to be confused by the turn direction arrows dispalyed at junctions. Remember 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.
Continue arrow
Remember that the "continue" arrow is merely informational. At this time, the routing server does not give the client any information about what to say for these. In the future, this feature may be enabled for specific circumstances.
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:
- There is something invalid with the junction
- It could have a short circular segment
- Very distorted in some way
- 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.
Communication
Because communication with the end user is not possible at this time via the Waze Map Editor Interface, the Wazer who submitted the Map Issue will not be notified when their Update Request is closed in the Waze Map Editor.
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.
If you find you cannot solve the Update Request without clarification from the Wazer, the best option is to send a PM via the Waze forums, using the username you see in the Editor. Keep in mind that there is no option to mark an Update Request with Missing Data or Pending Response as there was in Cartouche, so another map editor may work on and close out the Update Request.