A suggestion to enable Push questions (PQ’s) to communicate with drivers in order to solve map problems
I thought it would be really great if Area managers would be able to send PQ’s to drivers in order to get their help in resolving map problems.
For example:
• If I get a UR (in an area with low traffic) suggesting that a right turn isn’t enabled anymore and I want to verify this I might need to wait a long time until someone else will send an additional UR.
• Or if a road is suspected to be closed and I want to verify it before issuing an RT closure.
In such cases I would issue a PQ in WME.

This PQ would be sent to drivers (who marked in the application that they are willing to get such PQ’s):
• In the area
• In a route crossing the location
• In a route not crossing the location but suggesting them a small re-route to check the issue.
There are many variants on how to realize this suggestion. For example it could be realized by enabling a pre-defined set of questions in WME were you only need to update street names.
Also in order not to disturb drivers too much they can set in the application how many such PQ’s they are willing to get in one day / route.

Is this idea something that Waze devs are thinking about?
Is it on the list of future developments?
Thanks,

By: reuvenirony
Link to original suggestion: https://www.waze.com/forum/viewtopic.php?f=1525&t=220636

I am attaching a suggestion here to allow adding lanes in node that refer to a "far turn". Implementing this suggestion will solve all the problems of setting lanes (including extreme complicated junctions, H and # junctions) without the need for any heuristics! It will work at any junctions even if it is extremely complex with many auxiliary segments.

In the WME:
When defining lanes to a segment, turns are automatically displayed for the end of the segment with the segment names to which they refer.
My suggestion is to add an option for adding to lanes a "far turns". When you want to add a lanes for a "far turns", you will get an option to select the "far turn" and it will be added to the turns list for the lanes setting. You can define one or more "far turns".
The idea will look like this (attachment 1)
In the app:
The lanes will display as defined in the WME for that node (the number of lanes and the arrows).
When there are lanes at the node with "far turn", the arrows will be highlighted if the route passes in the "far turn".

An example of this type of solution is required:
The node:
https://www.waze.com/editor/?env=il&lon ... ts=1172278
The "far turn":
https://www.waze.com/editor/?env=il&lon ... des=800851
The lanes arrows:
(Attachment 2)

At this node, the arrows in the 2 left lanes (as seen in the attached photo) is for the next turn ("far turn").
The left-most lane should only show left and the lane next to it should show straight and left. Currently, the WME does not allow lanes to be defined correctly at that node. The proposal demonstrates how the lanes should be edited for this node.

by zeze13
Link to the original suggestion: https://www.waze.com/forum/viewtopic.php?f=1525&t=301202

With restricted areas, a level 5 (or Level X user depending on what the final level will be when released in production/country setting) could currently add a restriction to a level 6 segment.

Steps: find a rank 6 segment, draw an area on it => The segment is restricted.

This may be a WAD (similar to closures for people who have closure permissions), but it's still risky and lowers the protection of the rank system. If the user deletes the area restriction right after the map update, the problem cannot be identified without staff intervention.

Permalink: https://beta.waze.com/editor/?env=row&l ... =244207735

by: by bedo2991
Link to the original suggestion: https://www.waze.com/forum/viewtopic.php?f=1525&t=300254

With the recent release of version 3 of reCAPTCHA (the thing you may get to see when you log in and the system suspects you may be a bot instead of a user), it would be a great idea to upgrade to the latest version. We've had several users who have had to fill in the CAPTCHA protection every time for some weird reason (I suspect someone in their neighbourhood is to blame), which could be alleviated with the new system. The system now gives you a score between 0 and 1 to gauge how trustworthy the request is. That also means you can alter how strict the system will be.

The only downside of this means that you'll need to figure out what you'll do with people/bots with low scores. The reCAPTCHA v3 manual suggests requiring two-factor authentication or e-mail validation from such users, which would indeed help against wrong passwords, but probably won't protect the Waze map from scrapers (I suspect that is also part of the reason why the captcha was implemented).

Either way, I think it would be a good idea to already add some v3 calls in the background without adjusting any behaviour, just to get an idea of what scores the system generates.

By: Glodenox
Link to original suggestion: https://www.waze.com/forum/viewtopic.php?f=1525&t=270181