|
|
| (129 tussenliggende versies door 4 gebruikers niet weergegeven) |
| Regel 1: |
Regel 1: |
| =Update Requests=
| | Also it is best not to rely too much on <code>setTimeout()</code> or <code>setInterval()</code> for the inner workings of your script. If too many of these are being executed in userscripts, the user experience can suffer a lot due to performance issues. If you want to monitor changes to a certain element, consider using a [https://developer.mozilla.org/en-US/docs/Web/API/MutationObserver MutationObserver] instead. As an example, below is shown how to execute code whenever the settings tab is opened: |
| [[Image:Request_pin_open.png|left]] Update Requests are visible and contain useful information in the Waze Map Editor. Because the communication system with the end user is not built yet, we still rely on Cartouche for that part of update request processing.
| |
| | |
| | |
| ==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.
| |
| | |
| [[Image:Wme update request first click.png|600px]]
| |
| | |
| 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==
| |
| 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===
| |
| [[Image:wme update request meta info.png]]
| |
| | |
| To the left you will see the type of report, the date of the report and the username of the wazer.
| |
| | |
| ===Drive and Trace selection===
| |
| [[Image:wme_update request route and trace.png]]
| |
| | |
| 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 Waze requested route, or the users actual driven route, or both.
| |
| | |
| ===Report As===
| |
| [[Image:Wme update request reportas.png]]
| |
| | |
| 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 a Problem. Once you make once of these selections, you need to click the Save button.
| |
| | |
| ===Close===
| |
| [[Image:Button close.png]]
| |
| | |
| Way to the right of the Update Request information area is Close button. This closed the information area. It does not close the Update Request.
| |
| | |
| | |
| ==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. | |
| | |
| [[Image:Wme_update request zoom detail.png]] | |
| | |
| One of the following turn instructions is placed at each junction on the purple request route line:
| |
| | |
| * [[Image:Big direction forward.png]] - Continue straight/forward (client doesn't give this instruction by design)
| |
| * [[Image:Big direction right.png]] - Turn right
| |
| * [[Image:Big direction left.png]] - Turn left
| |
| * [[Image:Big direction exit right.png]] - Exit/Keep right
| |
| * [[Image:Big direction exit left.png]] - Exit/Keep left
| |
| * Blank - 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" 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, you will want to switch over to Cartouche and use that interface to enter notes to be emailed to the user. To get to the same location in Cartouche, use the [[Map Editing Tips and Hints]] page section "Open Waze Map Editor in Cartouche" bookmarklet.
| |
| | |
| Once in Cartouche, you may click on the Update Request and add notes. At this time, do not change the status to anything other than "Open" as this may cause the Update Request to disappear from the Waze Map Editor.
| |
