Update Requests
Hi All,
On a related note to the map issues thread I have a few questions about the finer details of Update Requests.
1) Is there an easy way to spot whether a UR in the editor was generated by the waze servers spotting issues with the map or a user report? I ask because for some URs such as this one it's very unclear why the UR was generated. I know that there's a "not identified" option but where possible I like to figure out why it was generated. In this case I can see that the user didn't take the exit which waze wanted and when they did exit the trace seems to show waze thinking they were driving down the wrong side of the dual carriageway.
2) What causes waze servers to generate an update request. I know that turning against a restriction and the "wrong" way down a road does but does ignoring waze directions or any other action?
TIA,
Andidy
On a related note to the map issues thread I have a few questions about the finer details of Update Requests.
1) Is there an easy way to spot whether a UR in the editor was generated by the waze servers spotting issues with the map or a user report? I ask because for some URs such as this one it's very unclear why the UR was generated. I know that there's a "not identified" option but where possible I like to figure out why it was generated. In this case I can see that the user didn't take the exit which waze wanted and when they did exit the trace seems to show waze thinking they were driving down the wrong side of the dual carriageway.
2) What causes waze servers to generate an update request. I know that turning against a restriction and the "wrong" way down a road does but does ignoring waze directions or any other action?
TIA,
Andidy
Re: Update Requests