Due to the new Zoom Level introduced in WME a few days ago, the candy cane stripes are now too thick at the various zoom levels.    
 

pvo11 wrote:Do you know what is in the new Road Closures layer? I did not see anything there. I guess it will show the same as my script, therefore my script will not be necessary in the future. Therefore the other possibility is to disable the script for Beta Editor.

Only L5+ can see the Road Closures layer. Currently, the layers look like this with Road Closures being default set to Shift+c as the shortcut:

Thanks for this script pvo11!
Works great, especially in combination with the livemap alerts script.

I'm seeing some odd behaviour for newly added closures. When a single segment is closed this script highlights all segments with the same name within the current view as being closed. With a refresh this clears and only the closed segment is shown highlighted.

Right now, you are hardcoded for the ROW routing server. There is a sample function located in WME Live Map Alerts Overlay that can get the server name from Waze.location.code (or W.location.code) since the routing servers differ.

I also like wlodek76's suggestion in trying to build the dashed line similar to LiveMap. While it's not the same red line as a segment without any information, we already have "red roads" for that purpose.

pvo11 wrote:This doesn't work. When I draw two lines with the same geometry, only the second one is shown. It doesn't mater if the second one is solid or dashed.

try playing with the opacity with line 2. You may end up with pink dashes instead of white, but it would be distinctive!

An updated for LiveMap Alerts Overlay has been released with the requested changes to layer and offset as well.

PesachZ wrote:It is also possible that there is some form of security in the Beta domain blocking the pull from the livemap domain, since they are on two different sub domains. I suggest you commuicate privately with the TB dev team, they likely had to deal with this too.

Actually... The only areas where Toolbox currently encounters the issue with the different Beta WME subdomain are the new forum inbox PM check and the overview map. There is nothing that impacts critical Toolbox functionality, so no one has looked at the cross domain issue. Supposedly there could be a workaround somehow by changing the document.domain to just "waze.com" or doing something with cookies, but nothing has been attempted yet. In any case, who knows how many unintended side effects this could have just running Toolbox--let alone a setup where someone may be running a dozen userscripts or extensions. It's easier to leave the issue alone considering the audience in Beta WME is a small subset of higher rank editors

Very nice script indeed..

Issue: Layer name conflicts with one on Beta Editor.

Suggest change to just "Closures"?