"Joining a Conversation"
If you are an AM or CM/CA then you might wish to introduce yourself?
"When closing a UR, please leave a message as to why you are doing so."
unless it's obvious?
maybe something about refer app issues to the support page/forum rather than try to help over a map conversation?
Not sure I agree about keeping replies short as some at least will be reading via email but I can see the point and won't press it.
==
Please can you let me have some more details so I can see if the map needs changing? If you go out of your way to respond to this you might prevent someone else going out of their way on the road.
If someone else closes your request by mistake, or if I close it due to no response after a few days, please use the UK forum at http://www.waze.com/forum/viewforum.php?f=55 to continue this discussion with me or another Waze editor.
Thanks for your time, David (dknight212).
==
Hi, we know of an issue with some motorway and major road junctions where users are taken off only to be directed to come back on again. This is a problem with the algorithms that Waze use and us volunteer map editors can do little about it. We are working with Waze to help them find a solution but for now all I can do is close your report. There is a thread on the Waze forum if you want to read more about this issue (see http://www.waze.com/forum/viewtopic.php?f=55&t=56560) or please contact me direct via a private message at the forum (my username is dknight212). Thanks for your report and I'm sorry I can't do more at this time. Safe driving, David.
==
Waze does not record the location of traffic lights or level crossings. While some GPS navigation systems offer guidance like "turn right at the next traffic light" the information is frequently incomplete, incorrect or outdated. The consensus view is that Waze should not record the location of traffic lights or level crossings.
Waze does take traffic lights and stop signs into account by noting the effect they have on traffic speed. Consider a traffic light with long waiting times. The road segment leading to that traffic light will have a low average speed. If the average speed (based on the average waiting time) becomes low enough, a longer route that avoids the light will become the preferred route. This has been observed in practice and is an example of emergent behaviour. Waze isn't programmed to avoid traffic lights but it will avoid slow roads; if the traffic lights make the road slow then Waze will avoid them.
Some drivers will regularly take longer routes—even winding through side streets—to avoid any stops or traffic lights. Waze has been known to suggest this, and also known to revert back to waiting at lights when better average speed information is collected from the side streets. But note that this can be less than optimal due to the turn delays discussed above.
Please contact me if you want any more information - https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1791397
==
Hi, this looks like Waze thought there were some traffic issues ahead and has suggested a slight detour. I cannot see any errors in the mapping. Because Waze's navigation is based on a combination of historic (based on time of day) and live traffic data, sometimes it will offer a suboptimal route like this. If a Wazer has just reported bad traffic conditions (even manually or automatically by driving slowly) Waze may try to avoid it even if the traffic has cleared by the time you approach the same road. If you can see the way ahead is clear then just proceed, your fresh data will then inform Waze that it's ok for other Wazers to be taken that way. Sometimes these types of detours are because Waze doesn't have enough speed data for the alternative route - if you have the time it can help Waze and other Wazers by driving the alternative, it will then know how bad (or good) that route is. You may even find a totally fresh route for yourself! If you know the alternative route is not permitted (eg because of turn restrictions) then please make a report to that effect. We can then change the maps and prevent Waze offering that route again.
==
Hi, we know of an issue in London where users fail to get routes at certain times of day across London. This is a problem with the algorithms that Waze use and us volunteer map editors can do little about it. We are working with Waze to help them find a solution but for now all I can do is close your report. There is a thread on the Waze forum if you want to read more about this issue (see http://www.waze.com/forum/viewtopic.php?f=55&t=55997) or please contact me direct via a private message at the forum (my username is dknight212). Thanks for your report and I'm sorry I can't do more at this time. Safe driving, David.
==
Hi, the turn into Millman's St is allowed although I agree it doesn't look like when approaching from the west. I get requests at least twice a week saying it isn't allowed so I've put together some details.
When viewed from this position (pointing east on King's Rd), you can only see the no entry sign for the exit lane of Millman's St:
but when you get to this position you can see the entry lane:
Waze will not give sufficient resolution to differentiate the two lanes here (the navigation line would obscure both) so there is little I can do except copy this information each time.
Please drive safely!
David
==
Hi, it's me again, David (dknight212). I'm closing this request to keep the map a little tidier and to keep our sanity levels nearer normality. Please use the UK forum at http://www.waze.com/forum/viewforum.php?f=55 to continue this discussion with me or another Waze editor.