I’m trying to figure out how best to handle this intersection: https://www.waze.com/editor/#?zoom=6&lat=40.02722&lon=-75.28691&layers=1925&nodes=54805238&env=usa
Most of the time, it is fine to turn left, when coming from the South, to stay on Old Gulph Road. As you will see if you look on Street View, however, the road runs through the creek, so when the water is either high or frozen (which is pretty often), the road is either closed or impassable. If we mark the turn as restricted, we’ll get frequent complaints and frequent SR’s suggesting that it should be allowed. If we mark it as allowed, there will be significant times when Waze will direct people to take a turn that they cannot take. (To make matters worse, it’s actually sort of hard to go around the block, so the turn that can’t be made might add 5 minutes or more.) Any thoughts about how best to handle?
Does it significantly reduce travel time over the next alternative? If not, may set it to a service or dirt road so waze will reduce its priority.
It does, actually. When it’s open, it’s definitely the way to go. But it’s closed so frequently (particularly with the winter we’ve had) that it’s not reliable.
Steinbdj — What an odd intersection!! Could you just rely on the drivers to report the road closed when it is closed? I’m not sure that the Waze editor has an option for a road like this.
Steinbdj — Just so you know I have marked this road as (Closed) for now. There was a UR reporting it closed for months. I restricted all travel across that segment. If we see a new report showing the road open again, we can reopen it.
Apparently the ford is closed Oct 15-April 15 so I have reopened that segment. It seems that allowing users to report it closed via the app and then us adjusting it based on the current URs in the area seems like the best option, unless you can think of a better one…