Segment restriction type that prompts user to confirm access (gates)
Currently we create gates using PR segments. However, this rarely has the intended effect. Those with access (say a gated community) don't get a route through a gate this is most convenient or worse, if all entrances are gated, then restriction is meaningless other than to ensure it's not a through-way.
I'm suggesting a segment restriction type that would generate a pop-up at start-state of a route asking if the user has access to a segment (gate) if that's the shortest route. Ideally, Waze would remember that for that user in the future. This could potentially be used for restricted locations like military bases, and private parking lots that require some sort of electronic access.
Thanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
Hi There- I would echo this - one base near us is not fenced, and despite signs up, waze keeps sending folks into an active live ammunition training area causing a safety issue for all involved.
I've thought about this as well and think it's very important. A possible solution instead of having to modify every PR segment is to allow us to draw a "restricted access polygon" and we draw a shape around the location including all the PR segments (an apartment complex for example). In this scenario, if mapped correctly, all traffic is directed to the guest entrance by default. Once the polygon is added, Waze will default to the entrance with the least penalties, but just like with multiple entry points, it can ask if you have the ability to enter at any entrance. If so, all PRs inside the polygon have the extra routing penalty removed for the driver.
This could be related to a better way to handle HOV routing. Similar pop up asking if you're eligible for HOV and treating it like a pass. Of course, there's definitely no suggestion like that on Centercode...
Marshall Griffiss commented
This is a very important issues that needs to be addressed