SuperDave1426 wrote:I was wondering if there's a combination of options that can be used to hide an open UR where the last comment was made by me, but only if that last comment was made less than x days ago. Once it gets over a certain number of days, it shows up again.

So, is there a way to make it do that?

You can try
Last comment made by me - no
Last comment less than XX days

This will only show URs which YOU commented on last, and your comment is more than XX days. It will not show urs you didn't comment on though.

I usually do this in stages, first hide all URs I already commented on, deal with what's left. Then filter as above.

This is a great script, and I love the functionality of the [ROADWORKS] URs. I like it so much I have suggested it be used to document when roads are reported to Waze to be closed for a emergency/construction/event type closures using the spreadsheet Waze provided for closing roads. When a road is known to be closed for a period we in the USA and any other country with this system in place can provide the details of the closure and the segments to be closed to Waze via a spreadsheet. Waze then implements the closure in the livemap/client app similar to if a user reported the closure through the app, with the candy bar roads and barricade icons. The same is true worldwide when there are road closure due to a mega event.

We have discovered that there is no way to know if a closure has already been reported to Waze though without having a champ with access to the request list sift through the requests looking to see if this one is on the list yet or not. Otherwise we end up duplicating efforts and reporting the same road multiple times. In WME there is no indicator if a closure has been reported, which would be helpful to editors working on URs in the area as well.

Another caveat of the system is that the segments may not be edited during the closure. The closures are implemented by segment ID and Junction ID, any edits which change the junction and segment IDs will circumvent the closure. For this reason Waze has asked that any segments reported to them for closure be locked as high as possible to prevent edits till after the closure ends.

For these two reasons we have started using URs to document the closure reports in WME, and for now we are doing that with the [ROADWORKS] tag. However this is not truly the intent of this feature, as these don't always have anything to do with actual road construction. I am asking if you would be willing to create one or two new tag filters with associated icons to be used for these closure reports. One would be [CLOSURE] it could have a barricade icon , the second if no too much trouble could be called [EVENT] and have say a balloon or other event type icon.

Twister-UK wrote:3.13 includes the features requested by PesachZ, sketch and bz2012, namely:

• custom markers for URs tagged as [CONSTRUCTION], [CLOSURE] or [EVENT]
• infobox popup when a restricted segment is highlighted

Both these new features are optional and can be disabled via the Misc tab.

Note: the restrictions popup doesn't (yet) display any comments - given the size of the box I didn't want to make it any larger than it may already get on segments with multiple restrictions, so for now it just displays the essentials...


Firefox+Greasemonkey version: https://greasyfork.org/scripts/1952-uroverview-plus-uro
Chrome Web Store version: https://chrome.google.com/webstore/deta ... mjcdghdphi

Thank you very much for the quick turnaround.

It may just be a publishing delay but the Google Chrome Webstore is still showing v3.12

Twister-UK wrote:

PesachZ wrote:It may just be a publishing delay but the Google Chrome Webstore is still showing v3.12

I'd forgotten to hit the publish button and left 3.13 stuck in draft status... 3.13 is now available from CWS

It's working now, thank you. Now I don't feel bad that was impatient and posted earlier.
http://img.tapatalk.com/d/14/08/10/e5y8y7u5.jpg
From left to right [EVENT] [CONSTRUCTION][CLOSURE] [ROADWORKS]

Would it not offend too many people if the custom UR icons for ROADWORKS, CLOSURE, etc. were set to checked by default?

Timbones wrote:Can we add [Closure] as well, if it hasn't been added already? This will be for documenting road closures that have been submitted to Waze.

It's already active as [CLOSURE] along with [EVENT], and [CONSTRUCTION].

Sent using Tapatalk for Android 4.4.2

Taco909 wrote:Very, very strange.

I disabled all scripts and started panning around on Zoom=0

Down in Orange County, I could view all URs including those over 30 days.
As I moved northwest into Los Angeles, I'd see some drop every now and then, until Whittier appeared at the corner of the screen. Around that area, moving closer to LA would cause ALL of them (even those displayed at the right of the map) to go blank.
Moving back into Orange County, they would come back slowly (not all at once)...
When I move to Los Angeles and move southeast, there is nothing on the map until I clear LA and then they start popping on.

Perhaps this is a limit of the Waze server to only display a maximum number of URs and to self-filter older reports when that number is exceeded? It certainly makes sense given the apparent progression.

I've never tested it carefully like you did, but I have experienced somewhat similar progressive display of URs in NYC as well.

Sent using Tapatalk for Android 4.4.2

Taco909 wrote:People still try to drive in NYC?

Only the very brave

Sent using Tapatalk for Android 4.4.2

pumrum wrote:Thanks for the great work! I thumbed through this thread but couldn't find if this had been asked before:

Is it possible to add an option to URO+ to disable the pop-up you get when you select "not identified" or "solved" to a UR where you have the last comment? The pop-up that says "This update request still has recent pending questions to the reporter. Are you sure you want to close it?"

I can close some times as many as 200 stale URs a day and this popup is a major time consuming nuisance.

I don't know if it's possible to disable, but I do know how to avoid it.

When you open a UR you are panning to close, click the "solve" or "not identified" first, then send your comment, then close. The pop-up only comes of you send the comment before clicking to solve or NI the UR.

This only works of you're about to send the first comment, if there's already an earlier comment waiting from before, this won't help.

Sent using Tapatalk for Android 4.4.2