Not seeing candy cane striping today...assuming it has something to do with the latest WME release this morning.

This looks very useful, though I'm mobile and haven't tried it yet.

I had an idea but I'm not sure how hard it would be to implement, or how resource heavy it would be. But here goes, feel free to shoot it down (or give it a try).

This script is drawing data from livemap which only displays closures currently in effect. However there could be uploaded closures which are scheduled to go into effect in the future which are currently still open. Those planned future closures do not appear in livemap (or in this script). However it is just as important that the segments of these planned closures do not get edited, because then the closure will never go into effect properly.

Therefore it would be great if the script could identify segments which are planned to be closed in the future as well.

Perhaps if a list of segments IDs which are planned to closed in the future was published, the script could check segments on the screen against that list and highlight them (maybe in a different color). The list could be unique by country. To reduce workload of the script.

What do you think?

Sent using Tapatalk for Android 4.4.2

pvo11 wrote:

PesachZ wrote: Therefore it would be great if the script could identify segments which are planned to be closed in the future as well.

This would be a very nice feature .

The list of segments is visible in the Google Sheets where the closures are entered in but these sheets are separate for each country and not open to public.
Additionally there is a problem with data filtering. I do not know the Google docs API in detail but I think there is no possibility to make a filter to rows, which should be read. This would mean reading of the complete table and filter the data in the script.
I am not very optimistic about the possibility to implement this feature without some Waze interface or adding this feature to the live map.

We solve this problem by locking the segments with closure to L4. This avoids editing segments by most of editors. Disadvantage of this solution is that the segments must be locked and unlocked manually.

The segment IDs are listed in the sheet for each row. they can be referenced to another sheet in the file to only show all the segment for closures which are current or pending. and that sheet can be published to be viewable by anyone. or it can be shared with the script author, depending on the needs for implementation. The difference would be if each browser is going to check against the live list, or the script will host its own version of the list on its own server somewhere. If this is something which the author(s) are willing to pursue, I'd be willing to try to help get the live list of segment IDs.

pvo11 wrote:I thing the easiest way would be to add the future closures to the live map data with some flag or start date of the closure. I guess it is easy change on the Waze side.

If there future closures will be shown on the live map (with another color) or not is another question. I guess it is no problem to send the data but not show in the live map.

Im not sure if we will be able to get waze to display it like that, though that would be nice. Maybe someone who knows can chime in. I was looking for a workaround.

I was going to post saying your layer is more visible, and should not be discontinued. But I see you already updated. Thanks

Sent using Tapatalk for Android 4.4.2

pvo11 wrote:

PesachZ wrote:I was going to post saying your layer is more visible, and should not be discontinued. But I see you already updated. Thanks

I've changed the layer name yesterday but the script still doesn't work in beta WME.

I made some tests today and there in something broken with ajax method I'm using to read the LiveMap data. Other scripts using the same method are affected too (for example: "WME LiveMap Alerts Overlay").

It is possible that the method is disabled by intent and such scripts will not work after the beta will be switched to production.
I will try to find some solution but I cannot guarantee anything.

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.

PHIL-IP63 wrote:Hi,
for me some closure on some segments are not shown.
Like here :
https://www.waze.com/fr/editor/?env=row ... =247846175
The closure on left segment is OK but on the selected one the closure is not shown.

Other example on these segments :
https://www.waze.com/fr/editor/?env=row ... ,150591495

I don't know why

Are they shown in livemap?

Sent using Tapatalk for Android 4.4.2

PHIL-IP63 wrote:Yes and no like you can see on the picture (clic on it).
http://img11.hostingpics.net/thumbs/mini_4039713IMAGE.jpg

If they don't show in livemap with stripes, this script won't be able to detect them. It's a Waze problem then, (unless the hidden closure isn't currently active)

Sent using Tapatalk for Android 4.4.2

Hi,
for me some closure on some segments are not shown.
Like here :
https://www.waze.com/fr/editor/?env=row ... =247846175
The closure on left segment is OK but on the selected one the closure is not shown.

Other example on these segments :
https://www.waze.com/fr/editor/?env=row ... ,150591495

I don't know why

Yes and no like you can see on the picture (clic on it).
http://img11.hostingpics.net/thumbs/mini_4039713IMAGE.jpg