bz2012 wrote:

PesachZ wrote: The candy stripe you see on these segments is a Waze Temporary closure, it is not a restriction, and therefore there is no pop-up.

Thanks for the info. I have even submitted some of those myself.

I have been running across such closures that have expired. I thought, at first, that they would 'automatically' be removed.

I posted follow up queries on the UR. No response.
I PM'd the submitter and was advised that there was no automatic closure, I should go ahead and close them. So I added the note 'closing expired closure flag' and marked them solved, but that does not effect the candystripe road segments. I thought it was a restriction that wasn't showing and blaimed URO+ but see I was wrong.

How should these candy stripes be removed?

Twister-UK wrote:

james890526 wrote:Currently using URO+ v3.40, but I can't seem to get the "Undo last hide" & "Undo all hide" button working. Is it disabled by default (not available yet)

Those two buttons are only enabled when you've hidden a UR or MP marker by clicking on the "Hide for this session" link in the UR/MP popup.

Timbones wrote:

Twister-UK wrote:How? With no scripts running, nothing appears in the native UI and Ctrl+A doesn't do anything when a roundabout segment is selected.

I was just quoting the release notes. Maybe it's only named roundabouts that can be selected, but this can be done in production anyway.

I'll post a suggestion to allow unnamed roundabouts to be selected too.

Olestas wrote:Do we now name roundabouts?

dude463 wrote:

voludu2 wrote:

Twister-UK wrote:If I can find some examples of such PURs, so that I know what properties are set when they're in this state,

I assume you don't even need editable area to see what you want to see?

Here's one created (in the wrong location and with incorrect address), updated, and locked by avsus for an ad campaign.
https://www.waze.com/editor/?env=usa&lon=-75.58383&lat=39.96772&zoom=5&venues=186384784.1863913373.1597752

Here is another one, created by wazers but then updated and locked by avsus for an ad campaign:
https://www.waze.com/editor/?env=usa&lo ... 304.471430

Does anyone know if they can talk to avsus? They're screwing up locations of Baskin Robbins left and right. Sometimes about a mile off. Usually duplicated for ones that are correctly located too, so sends Wazers to the wrong location.

nzahn1 wrote:

sketch wrote:

Twister-UK wrote:It's something which has been present since the early days when URO was still just a baby script used by a handful of UK editors. Over here, speed cameras are never set to anything other than a multiple of 10MPH, but back then there were numerous cameras defined in the UK map data with speeds that were slightly off, e.g. 29MPH or 31MPH.

Understood. Would it be possible to change it to a "multiple of 5" rule? Speed limits in the US are commonly set to multiples of 5. Should be a simple fix and remove a whole bunch of false alarms in the US.

I will note it is common practice (in the law I think) in my area for speed cameras to have 12 mph leeway, so I COULD see an editor adding a warning at 42 mph for a camera in a 30 mph zone. Not saying I have seen this, or that it should/shouldn't be done, just that it follows a certain logic too.

russblau wrote:BUG: In Chrome with Tampermonkey, URO+ 3.46: every time I load the Editor, the UR filter setting for Hide URs with no comments from me is checked. I uncheck it manually, but the next time I load the editor it is there again. (Note: the other filter is one I did set the last time I used the Editor.)

URO.png

Twister-UK wrote:3.57 is mostly a bunch of fixes for WME Beta users. For non-beta users, the only change is that URO+ now doesn't even attempt to run in practice mode, as opposed to doing it's best but not really working quite the same as when you're logged in. In all honesty, the only reason I ever tried getting it working in practice mode was to let me do some debugging of stuff on the US server in the days before I got an AM area set up over there, and with all the headaches of trying to keep on top of the changes in the beta I just don't have the time to expend on attempting to maintain practice mode semi-compatibility, so the only sane option was to kill it entirely. If anyone is *really* inconvenienced by this change, please get in touch...

Anyhoo, back to the changes for beta users. The big change is that it now works again, at least on my FF and Chrome setups. Feedback would be welcomed from any beta users who saw problems with previous versions, particularly Chrome users who seemed to be hit hardest.

Additionally, there's now an option in the Misc tab to hide the stupidly large user info section at the top of the sidebar, and the links in the menubar at the top of the screen (livemap, support etc.) are now rewritten to point to http://www.waze.com instead of being relative links which have never, ever, worked on the beta server...


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