Here's an example (two views of the same closure)...
http://img.tapatalk.com/d/13/03/14/e9a5uny5.jpg
http://img.tapatalk.com/d/13/03/14/qa2a6eju.jpg

This just happened to be my view of the closure. I've yet to run into an instance of someone else reporting a closure. This particular one was given a "long term" status for closure due to the road being torn out completely for construction that will last months. It stayed visible to me longer than a few hours, but by the next day was no longer visible.

Of course, I changed it thereafter. I merely drove by to verify the closure I'd heard via news reports.

I selected though what I felt was most representative of the situation which in this case was "long term"... and that didn't last 24 hours. That's the kind of thing that I could imagine would frustrate a new user if they have to repeatedly issue a closure report for a particular stretch.

This is more of a wishful thinking feature request, but if something is going to be closed for more than a few days and that type of timing status was selected in the user report filed in the client, it would then trigger a system error marker in the editor. From there area managers could take the necessary action and investigate what needs to be done to handle the road closure.

Has anyone had any success at attempting to close an interstate ramp or similar acute deviation from the route being traveled?

I made an attempt last week at a mapped weigh station with an exit ramp that was closed due to construction. The ramp's close "x" icon wasn't far enough apart from the interstate (forward) section. If I'd pressed the only closure x there in the diagram, it would have resulted in me submitting the interstate and not the ramp was close down.

The client may need to factor in shallow angles and better offset the buttons in those cases.

This is the ramp that I'd encountered. The angle is set so that it would properly give an "Exit.." command based on the geometry, but you can see if you highlight the interstate segment prior that, the turn arrows fall too closely together.

https://www.waze.com/editor/?zoom=6&lat ... s=68820827

So is this more a case of needing a wider angle, or a case of an acute angle being problematic for the road closure feature that works better with perpendicular intersections?

I'm going to look at a variety of angular intersections, but you can see in the images below, a ramp will be very difficult or in some cases impossible to close given where the touch points are rendered.

It may not be possible, but if a road segment was treated like the touch points for activating a closure, you could tap on the ramp segment itself to activate a closure selection.

http://img.tapatalk.com/d/13/03/22/evutazyv.jpg
http://img.tapatalk.com/d/13/03/22/a7ahabyt.jpg

Has anyone else attempted to use the closure feature at an intersection that's more complex or for a ramp or other acute intersection other than a standard perpendicular ones? Is a verified slightly less than 45° degree angle proven to work for the closure feature?

CBenson wrote:So I was approaching another road that was closed today. I was a red light looking at the police barricade on my left. But as the left turn is normally restricted there, waze would not give me the arrow to close the road. Does the road have to be closed from each direction at an intersection to be effective?

Yes, from my testing you're only marking it as closed from your perspective and turning onto that road, so in that case since the turn isn't allowed from that direction you'd have to get yourself in the opposite lane in order to be able to close it. It is a good question though if let's say an intersection has all turns allowed if reporting would close down a segment for both ways (but I'm guessing it may only impact from the turn perspective based on how you're traveling the roads).

I've had some experiences where editors have already gone in and restricted turns in construction zones that would otherwise have been okay and that action will take and block the road closure as well, but obviously that approach is more beneficial for long term projects since it actually forces routing around those turn restrictions due to construction.

It's not ideal... but then again we already have similar types of issues such as split roads and reporting hazards. You can only do so for the half of the split road that you're driving on.

Had a chance to finally test out closures on an interstate. I-80 E in Council Bluffs, IA is closed for a day or so based for repairing a major hole that developed in the interstate resulting in emergency closures.

Doing routing tests afterwards showed Waze sagely steered around the closures to reach the destination in the next best possible way.

http://img.tapatalk.com/d/13/10/10/evy7evan.jpg

http://img.tapatalk.com/d/13/10/10/y7ymejad.jpg

Recently, I have been fixing a lot of URs and occasionally advising the reporter that, for temporary road construction, they should report a closure rather than a map issue.

The only problem is that when I have tried to actually report a closure, I have found it very difficult to do.

When I try while located before the closure, often I can not click on the proper arrow. For example, when an exit ramp is closed, such as this one: https://www.waze.com/editor/?zoom=5&lat ... 23&env=usa the 'arrow' for continuing on US59 covers the arrow for the exit ramp and the ramp can not be selected.

And, of course, If I am already ON the ramp, the only closure I can select is https://www.waze.com/editor/?zoom=5&lat ... 68&env=usa
So, I can understand now, why the drivers are not using the Report closure.

Suggestion:
When a driver selects "report closure" , WAZE should ASK 'ahead of you or behind you?'
It should then go through a list of questions to narrow down the closed segment selection.
I should have been able to say 'ahead', 'to my right'
or 'ahead', 'to my left'.
Or 'behind me', 'on the road taken'
or 'behind me', 'on the road not taken'
or something similar to this.