Page 1 of 3

Waze is ignoring event closures

Posted: Sat Feb 22, 2014 3:51 am
by
At least cross-street closures.

http://img.tapatalk.com/d/14/02/22/u7epapyd.jpg

St Charles is entirely closed. Crossings should not be allowed at all, per the event entry presentations.

There is, at the least, one actually-possible route during the closure.


Sent from my iPhone using Tapatalk 2

Re: Waze is ignoring event closures

Posted: Sat Feb 22, 2014 11:14 am
by deeggo
We have seen the same here. If you consider that these are segment closures, it's working correctly. The question is if it's desirable.

Re: Waze is ignoring event closures

Posted: Sat Feb 22, 2014 9:24 pm
by deeggo
You're right it's in the presentation. We know it's just the segments with the given IDs that are closed. So it's no surprise they didn't close the nodes in between automatically.

Re: Waze is ignoring event closures

Posted: Sun Feb 23, 2014 7:21 pm
by deeggo
I don't quite understand what's making you get a route around the closure. Is it by approaching it enough, or by simply driving? Or difference livemap / client?

Re: Waze is ignoring event closures

Posted: Tue Mar 04, 2014 2:21 pm
by deeggo
Noam, then the presentation should be changed to reflect this.

Re: Waze is ignoring event closures

Posted: Sat Feb 22, 2014 2:17 pm
by htahta
Jep Always close the feeding street or the exiting street.

Re: Waze is ignoring event closures

Posted: Sun Mar 09, 2014 3:56 am
by LeighGr
For the Cape Argus, I'm not seeing a single closure on the client nor livemap, and both are quite happy routing me over roads that have been closed since midnight (6 hours ago).

I'm not venturing out there as it's absolute chaos at the start, though I've messaged a few Wazers I do see out there making their way to the start, asking if if they see any road closures.

I'm also not happy with the fact that crossing aren't handled as originally advertised. I'll just have to get it right next year, when hopefully I'm one of the 40,000 nuts out there.

Re: Waze is ignoring event closures

Posted: Sun Mar 09, 2014 9:04 am
by LeighGr
Now this is very confusing. It was pointed out to me by another editor that the road closures are now appearing, but about 10 hours late, and I can see them in livemap from the finish, going 3/4 of the way round back to the start.

Maybe it needs the lack of traffic on the roads to kick in??

It will be interesting to see if the closure are removed at the listed times. If not, then I suspect a time zone conversion snafu.

Shall keep monitoring.

Update @12:40: Closures appear to be removed at the correct time, from what I can see from livemap.

Update @20:30: All closures have been removed. Looks as if it was just a late implementation, as the "Avoid traffic from the cycle tour" notification was only sent at 09:46, by which time the elite group, who left at 06:15 and took just over 2 and a half hours to complete the 109 km route had long since finished.

Many thanks to all at Waze Support involved. This process can only get better.

Re: Waze is ignoring event closures

Posted: Sat Feb 22, 2014 1:34 pm
by petervdveen
deeggo wrote:We have seen the same here. If you consider that these are segment closures, it's working correctly. The question is if it's desirable.
I think it is.

If you want to close the junctions, then just close the connecting streets.

Re: Waze is ignoring event closures

Posted: Sat Feb 22, 2014 10:21 pm
by petervdveen
sketch wrote:Besides, having to close all the various parade routes is hard enough. Having to add hundreds upon hundreds of cross streets is absurd.
But what if you can cross?
Then it will be impossible.

I think overall leaving it as it is is the easiest.
Btw, you know you don't have to do it street by street?
Just selecting a few extra streets isn't that a big job, I think.

Re: Waze is ignoring event closures

Posted: Sun Feb 23, 2014 7:45 am
by petervdveen
Absolutely agree with that.