So we have this feature now, are we going to add this to the woolwich ferry, this is certainly one of the main examples I can think of in the UK where this would be useful.
Now we time restricted tolls for the dartford tunnel. 
Yes, for ferries which are not 24 hours, timed restrictions would be appropriate to use. I think that first departure to last arrival would work best.
Woolwich Ferry: http://www.royalgreenwich.gov.uk/info/200078/public_transport/61/ferry_services (thanks Iain)
via mobile
Might be useful for prolonged periods of overnight closures for roadworks too.
I’ve added the time-based restrictions for the Woolwich Ferry. I’ve tried to account for the times of last services each day - so whilst the opening times are (for example) 6:10am to 8pm Monday to Saturday, I’ve set the evening closing times to be 7:45pm (for the last southbound ferry), but earlier than that for northbound.
I’ll try some tests after we get the next update.
I’ve also added closures for Christmas Day, Boxing Day and New Years Day. However I don’t yet know for sure how overlapping restrictions work: whether they all “add up” or whether they take priority depending on where they are in the list.
Hi,
Needs to be done for Hyde Park and the North & West Carriage Drives etc as they close at night… 
Des. . . 
and Richmond Park
I added that to my list last night. We’ve got a separate thread somewhere on that one and the issues raised by dawn till dusk opening.
Sent from my GT-N7100 using Tapatalk
Further to my earlier comment, the Highways Agency site http://www.highways.gov.uk/traffic-information/ has a list of overnight slip road closures for the M25 (and many other roads too). Now that we have the ability, we ought to be recording the overnight closures to major roads, it’s probably one of the most useful things we can do on Waze.
However, most of the afflicted segments are locked at L5. Is this work going to be handled by Country Managers?
Waze has repeatedly said that we shouldn’t use timed restrictions for short term road works, and that they have “something better” in the works. However, given that we have nothing else at the moment, we could trial it in a few places.
Advantages: roads can be closed / reopened at set times without a map update.
Disadvantages: if a road reopens early, then restrictions can’t be removed without map update.
It might not be worth doing for night closures of Motorways, as they tend to be very well advertised on the roadside message signs. Maintaining the restrictions may become far more tedious than useful.
The closure may be well advertised but the best alternative route often isn’t. Especially for journeys for which the motorway route is normally out-of-the way but faster. When the motorway is closed, the best option is probably going to be the direct route rather than still diverting towards the motorway but then following a slow road close to it. If people are going to use Waze for navigation at night, it would function much better if it had this information.
I do agree maintaining the updates would be tedious though. 
If we do used timed restrictions for road closures, we should definitely mark them with URs like we do for roadworks.
I happened to be talking about this exact thing to a Waze user yesterday.
She was in a position last Wednesday evening where Waze was effectively useless for her. She was coming round the M25 ACW at about 11pm. The M25 was closed between J10 and J8 but she wasn’t aware of that in advance and the roadside signs on her approach didn’t make it clear which junction it was reopened from. She simply knew that the M25 was closed at J10 and she was being diverted off.
She didn’t have much of a choice but to follow the ridiculous diversion route through South London as Waze kept trying to send her back to the M25 which she knew was closed. There was a much faster diversion route available to her destination and had Waze known the M25 was closed between those junctions it would probably have offered her that route at the outset and got her home an hour quicker.
I know that she could have pressed the Routes button to get another route or picked the avoid motorway option to force it but she didn’t know she could do that or was particularly keen on fiddling with the phone while she was driving and I daresay many users are in exactly the same position.
I’m fully in agreement that it’s going to be a pain in the arse to keep track of but many of us knew well in advance that there were overnight M25 closures and we could have set it up to close and reopen at the advertised times. I’m not saying it should be universal policy to put in scheduled closures but it should at least be considered for full closures on the main trunk network.
I had similar experience in summer when I drove from London to Newcastle through A1. I was diverted twice due to 2 separated closure at night. It’s really pain to be diverted and asked to join back A1 and then I was diverted again :? It’s worth to try to use time restrictions for night closure IMO.
On that note I have always wondered whether the routing engine takes into account time of travel to a certain segment.
So for example if I was travelling from Gatwick to Dartford coming off at junction 1, typically a 30 minute journey, lets say leaving at 9:30 and lets say junction 1 closes at 10pm, would it take into effect the closure as it would be closed by the time I get there, OR will it not take it into effect as the junction was open at the time of planning the route?
Any junction closings happening soon so we could do some testing?
I plan to test it with the Woolwich ferry. I work about 40 minutes from there, so I’ll be able to do some tests starting from around 7pm to see what happens - once we get an update.
It has been suggested to me that Waze tries to judge whether a route is available or not based on the restriction at the estimated time of your arrival there. That would certainly be the best way to do it but would inevitably be an approximation based on ETA.
I suppose that would be the next question, this one might need to go to waze, but another hypothetical situation.
You are heading for the last ferry, but get held up, the ETA changes, will it realise and and reroute, or will it carry on regardless…
I’ve tested it on livemap by putting different Origin points. One take less that 30 mins and one more than 30 mins to the destination (with time restriction). It seems it works. That means it takes into account time of travel.
Obviously we can’t test it on livemap and may have to test in physically or waze has to answer it. However, it should work I assume if the previous case works.
That’s good to hear.
Just thought of another bad thing about temporary closures. If say a junction is closed you will get taken off the motorway a junction early or late. If it’s early as you have not been told why and may not have seen the warnings you might think that’s not right and ignore it. Only to find out to late. Hopefully the new tools will allow for some form of notice of why the route is different than possibly expected.
I know it all books down to keep an eye on the signs but we all know half of drivers don’t
Sent from my GT-I9505 using Tapatalk
Based on tests that other people have done, it seems that Waze will notice the change in restrictions when it recalculates the route, but this might not happen immediately and may need some other trigger to occur.
via mobile
I have discovered that you mustn’t be too verbose in the description of a time restriction. If you are, it appears to be OK, but later you get “an error occurred while saving - please try later”. It took me a while to work out why I was getting that helpful diagnostic. :roll: