Lucky you! In the cases that you saw, did it actually prevent routing?

gerben wrote:I managed to close the N35 singlehandedly. It has a l5 travel lock.

Did you check that it was blocked for others too? Cause blocking yourself works perfect.

petervdveen wrote:Just noticed today all roads where closed for the triathlon in a village nearby.
So it's working after al

Where is that? Just curious how it looks, I've never seen an event in the wild.

Never mind, found it in the confirmation sheet.

It's a pin-frenzy!

foxitrot wrote:

sketch wrote:So there's no real need for the routing server to be time-zone-aware except perhaps for proper ETA calculations on routes that cross time zone lines.

Someone sitting near a time zone line may be willing to try this out: two similar TBTRs valid since e.g. 10:00 at two sides of the line, a route through them at 8:30, 9:30, 10:30, 11:30 and note, which one is when taken.

When helping with the scheduled blocks for the Mexico City Marathon I had to provide groups of segment IDs and closure times for each group... I guess this could be used to set different times the correspond with the time in each side of the time line.

sketch wrote:

foxitrot wrote:

sketch wrote:So there's no real need for the routing server to be time-zone-aware except perhaps for proper ETA calculations on routes that cross time zone lines.

Someone sitting near a time zone line may be willing to try this out: two similar TBTRs valid since e.g. 10:00 at two sides of the line, a route through them at 8:30, 9:30, 10:30, 11:30 and note, which one is when taken.

Staff informed us that TBTRs are not time zone aware, I believe.

My extrapolation is based not only on personal experience and conjecture but also on that statement from staff.

This is a screenshot of some of the data that I was asked for when preparing for the Mexico City Marathon so I still maintain that for events it would be easy to use as a way to manage different time zones.

You can find it here:
https://www.waze.com/events/unready
As far as I know the events with no "Created by" are included by the Staff.

From one local event I've personally tested a month ago - there were looooads of report pins, unfortunately just a few of the requested segments were red-white-dashed and too often it was perfectly possible to obtain a valid route along the segments-to-be-closed. I've written an extensive report with many screenshots to Waze, they thanked for it and that was it. I have a hope that now it is better tuned...

MReiser4670 wrote:With the number of segments affected, I have a feeling there will be hundreds of pins showing up on the client. Not sure how that's going to look?

Isn't there some 20 or 40 pin limit to be displayed, similarly to the wazers' icons?