Road Closure discussion thread

These forums are specific to the Waze mobile app. Post here if you experienced a problem while using the app, have a question about the app functionality or a feature such as navigation or search.

Moderators: Unholy, bextein

Re: Road Closure discussion thread

Postby fvwazing » Fri Jul 26, 2013 1:54 pm

Over the past months I may have seen 3-4 roadclosures (client-created) in the wild - that is very, very few for the whole of the Netherlands. And it isn't that we didn't try!
Waze jezelf!
600K+ edits
AM for some 25.000 km² around Maastricht, the Netherlands
iPhone 3Gs / iOS 6.0.1
fvwazing
 
Posts: 3589
Joined: Sat Nov 14, 2009 2:48 pm
Has thanked: 412 times
Been thanked: 379 times

Re: Road Closure discussion thread

Postby fvwazing » Mon Apr 22, 2013 3:40 pm

Curious - in the first image it looks like that short segment is "skipped" and the next (left)turn is offered.

"Others will be routed around it" is misleading at least.
Waze jezelf!
600K+ edits
AM for some 25.000 km² around Maastricht, the Netherlands
iPhone 3Gs / iOS 6.0.1
fvwazing
 
Posts: 3589
Joined: Sat Nov 14, 2009 2:48 pm
Has thanked: 412 times
Been thanked: 379 times

Re: Road Closure discussion thread

Postby fvwazing » Sun Mar 10, 2013 1:24 am

jwkilgore wrote:The solution is simple:
- Expand the closeable roads to include 3-4 segments in either direction starting at the one you're on, including the segment you are on.


I am afraid the solution is not that simple. Yes, there are situations where your scheme could help in reaching at least more of the segments that you want to report closed. Even the typical #-crossing is impossible to close now. But with more options to choose from than the current "solution" it would take patience, a precise control over your fingertip and maybe even advanced gaming skills ;) . It takes a very cool head to do that on the freeway, at the same moment slamming your bakes to avoid running into a jam, with ambulances and firetrucks whizzing by, police motorists clearing the traffic as it rolls, at night and in bad weather.

And it is not enough that YOU manage to do all that, some other Wazers have to confirm/copy your actions as well.
Waze jezelf!
600K+ edits
AM for some 25.000 km² around Maastricht, the Netherlands
iPhone 3Gs / iOS 6.0.1
fvwazing
 
Posts: 3589
Joined: Sat Nov 14, 2009 2:48 pm
Has thanked: 412 times
Been thanked: 379 times

Road Closure discussion thread

Postby fvwazing » Thu Mar 07, 2013 11:46 pm

No, as in my typical freeway-examples above you need 3 or 4 closures for a stretch, each of these confirmed by a number of Wazers, within a reasonable time. Will not happen soon, and until every mousehole is closed expect routing to bend over backwards to send you into that sheet of ice.
Waze jezelf!
600K+ edits
AM for some 25.000 km² around Maastricht, the Netherlands
iPhone 3Gs / iOS 6.0.1
fvwazing
 
Posts: 3589
Joined: Sat Nov 14, 2009 2:48 pm
Has thanked: 412 times
Been thanked: 379 times

Road Closure discussion thread

Postby fvwazing » Mon Mar 04, 2013 10:11 pm

CBenson wrote:
fvwazing wrote:Wazers on the blue track will report THE NEXT SEGMENT closed. As soon as that block works, Wazers coming from the same direction will be guided off the highway ONE EXIT TOO EARLY and into the roadblock - over the green track.

So if I understand this correctly, the reporting wazer will be immediately rerouted based on his/her own closure report. But if on the freeway, where the next segment is just the freeway segment between the off ramp and the on ramp, the reroute can be straight back down the on ramp to the closed freeway. It seems that is what howsmith reports here.




In my first example I assumed that at least the traffic coming down from the last-offramp-before-the-closure would be guided to the next junction after the actual accident, some km further. All traffic coming from behind would be guided as per stupid deviation around the jam reported by the original reporter (assuming there is a jam before the closure; typically there is) and would have to report some closures more.
In MY almost-perfect part of the Waze-world, off-ramps are not connected to on-ramps wherever possible - howsmith ran into a ramp that is clearly mis-configured and in his case he would have had to report another closure - of the onramp.
Anyway, you need a lot more closure-reports for a single stretch of freeway.
Waze jezelf!
600K+ edits
AM for some 25.000 km² around Maastricht, the Netherlands
iPhone 3Gs / iOS 6.0.1
fvwazing
 
Posts: 3589
Joined: Sat Nov 14, 2009 2:48 pm
Has thanked: 412 times
Been thanked: 379 times

Road Closure discussion thread

Postby fvwazing » Mon Mar 04, 2013 5:21 pm

I just did some testdriving. My area is so clean that I had to make a 20km detour to reach a segment of freeway with extraneous nodes. Well, I could have saved myself the trouble. It is indeed impossible to reach the next split if you are behind an extraneous node. Worse than that; if you are behind a "join" you can select the joining node - but the segment that is reported closed is the one before the join, the segment you are driving at the moment of reporting. Counterintuitive, that is.
Waze jezelf!
600K+ edits
AM for some 25.000 km² around Maastricht, the Netherlands
iPhone 3Gs / iOS 6.0.1
fvwazing
 
Posts: 3589
Joined: Sat Nov 14, 2009 2:48 pm
Has thanked: 412 times
Been thanked: 379 times

Road Closure discussion thread

Postby fvwazing » Mon Mar 04, 2013 1:52 am

I have no positive confirmation, though I asked around in our local forum (would be a miracle by itself, given the participation here). I have not had the opportunity myself to report a valid closure of a freeway. I estimate that 40-50 Wazers were involved in the incident, over a timespan of 5 hours. No doubt that many are not aware of the functionality (I saw a brief reminder of it pop up once, a minute after I drove off). And of those who are aware - not all find the right buttons even though that jam was standing still. Kind of a "Drake's equation" here. What are the odds?
Waze jezelf!
600K+ edits
AM for some 25.000 km² around Maastricht, the Netherlands
iPhone 3Gs / iOS 6.0.1
fvwazing
 
Posts: 3589
Joined: Sat Nov 14, 2009 2:48 pm
Has thanked: 412 times
Been thanked: 379 times

Road Closure discussion thread

Postby fvwazing » Sun Mar 03, 2013 9:45 pm

Yeah, BEFORE a split that is. But I must admit I will have to check that hypothesis, if true it snaps everywhere you have extraneous nodes - every basemap has millions and it would be a very big oversight if that meant you cannot "reach" the next split in the road.
Waze jezelf!
600K+ edits
AM for some 25.000 km² around Maastricht, the Netherlands
iPhone 3Gs / iOS 6.0.1
fvwazing
 
Posts: 3589
Joined: Sat Nov 14, 2009 2:48 pm
Has thanked: 412 times
Been thanked: 379 times

Road Closure discussion thread

Postby fvwazing » Sun Mar 03, 2013 9:23 pm

It wasn't the case in my example, but I just remind that the practice of inserting a short (15m) segment in a freeway as means of a "wayfinder" segment or to force directions is not compatible with reporting closures as it works now. [sorryhavenolinkathand]
If it stays like this we will have find different workarounds for those.
Waze jezelf!
600K+ edits
AM for some 25.000 km² around Maastricht, the Netherlands
iPhone 3Gs / iOS 6.0.1
fvwazing
 
Posts: 3589
Joined: Sat Nov 14, 2009 2:48 pm
Has thanked: 412 times
Been thanked: 379 times

Road Closure discussion thread

Postby fvwazing » Sun Mar 03, 2013 5:47 pm

Yup, if it is clear 100% from the drivingpattern (going left or right) that you cannot have been on the freeway the jam should not get reported or even get revoked. And the stickyness should be related to the actual GPSaccuracy (which can be as good as 7m). These are cuckold issues that, by never addressing, now prevent further development. (Don't get me started!)
Waze jezelf!
600K+ edits
AM for some 25.000 km² around Maastricht, the Netherlands
iPhone 3Gs / iOS 6.0.1
fvwazing
 
Posts: 3589
Joined: Sat Nov 14, 2009 2:48 pm
Has thanked: 412 times
Been thanked: 379 times

PreviousNext

Return to Waze App

Who is online

Users browsing this forum: Google [Bot]