This is becoming too difficult to do. I used to be able to just declare a road closure on my mobile app. Now that I have a Hyundai, it won’t let me use my mobile app on the road. This has limitations. 1: You have to be in the area of what you’re reporting in order to report it. 2: a Road Closure isn’t an option on the vehicle-based version of the app. So, the only way I can report it is on the website: or so I thought. This is a major closure that will last until the beginning of December. You’re realy making me want to use a different app, because now I need “permission” and an unlock to Level 3. Really? I can do it myself on the mobile app, but not on the website? I hope everyone else this is affecting appreciates how difficult you’re making it to notify the community of a road closure.
So, there’s 2 different issues in this post. Both are, to some extent, beyond the control of the local Waze editing community.
In app closures from Android Auto/CarPlay are not possible because of safety features built into the OS. Waze corporate has zero control over that, as AA is a separate entity within Google and Apple pretty much does what it wants because they’re Apple and they can. Also, an in-app closure sent from the phone does not always result in a closure being entered into Waze. There is an internal validation process that prevents folks from closing a road to everyone just because they don’t like cars driving through their neighborhood.
As for the second issue, it’s always been the case that closures are generally limited to level 3 or higher editors, and an editor can only close a road of their level or lower. See the above internal trust issue for a very dumbed down reason.
We’re happy to input the above closure right now, we just need a time frame. If you’d like to join us in the Plains Region Discord, we can simplify this process quite a bit.