Offline routing is even worse than I thought… Before I went looking for a timed restriction against which I could test whether offline took ETAs into account, I thought I might just do a quick check against a 24/7 restriction, just to make sure that at least was being handled correctly.
Nope. Even after making sure I’d refreshed the map data for that area, and checking that in online mode it was indeed being respected, as soon as I switched back to offline mode and asked for the same route, the app completely ignored the restriction and gave me a route that went straight through it like it was just any other regular segment.
So if offline routing is happy to ignore a restriction that it should never, EVER, route through, I feel fairly confident in saying that it would make no difference whether or not it does at least try to work out the en-route ETAs for each junction node reached, because it’d almost certainly then simply ignore any timed restrictions it finds along the route anyway.
The more I learn about offline routing, the more I wonder why Waze bother to keep it enabled - it can’t handle realtime closures, it can’t handle u-turn prevention (and probably also can’t do BDP given that’s implemented using similar rules/segment “hacks”), and now it can’t handle segment restrictions either… At least it’s aware of turn restrictions and what one-way segments are, so it’s not a total disaster area, but given how limited it is I do have to wonder if the benefits it provides in enabling some form of route to be generated even without network coverage are offset by the risks of said route then being completely and utterly wrong due to all the limitations above…