Beveridge Lane, Ellistown Closures

Hi

There are three weekend closures scheduled for Beveridge Lane, Ellistown over the next 3 weekends.

The road closure requests have been logged on the road but just need actioning please:

https://www.waze.com/editor/?env=row&lon=-1.35193&lat=52.69871&layers=12677&zoom=4&mode=0&mapProblemFilter=0&mapUpdateRequestFilter=0&venueFilter=1&segments=316845355

Thanks

Problem processing this. :frowning:

Hard to explain without a bit of background. Waze really has two maps. There’s the one you see in the Editor. And the one you see in the app, which is used for routing. The app map is refreshed from the editor map every day or so (when the process is working smoothly, sometimes there can be delays). You can see when the last refresh happened by looking for international (INTL) tile updates here.

Now even though closures are input using Editor, they go directly onto the app map. Which means that if the segment in question has been edited since the last refresh, Waze gets very confused and refuses to record the closure. This is what has happened here.

So I can’t close the correct road. What I have managed to do is close segments either side of it. This is fine for most purposes; we really only want to stop Waze using the road for through traffic, and this will be achieved.

A problem could arise for people trying to navigate to or from a point in the incorrectly-closed sections. To mitigate this, I’ve closed them one-way only, in the direction away from the closure. This should mean people navigating in are not affected. People navigating out will just have to drive a bit before Waze will calculate a route for them.

I’ve only input this weekend’s closure. I’ll come back next week, by which time a “tile update” should have happened, and I’ll be able to do the next two properly.

Ian

Thanks for sorting and for the explanation :slight_smile: