[Script] UROverview Plus v3.133 (20180412)

[iainhouse]

Hmm, I wonder if we should do the same here in the US, and if so, should we just adopt the unfamiliar-to-us [ROADWORKS] tag, or ask for a US-specific one.

I'd feel quite proud if you did. I'm sure Twister-UK could filter [CONSTRUCTION] as well. Mind you, we have to put up with Freeways and Parking Lots, so turnabout is fair play.

It's worked so well it was the basis for my proposal for a new type of editor comment </shameless plug>. Of course, HQ say they're working on something else - I'm sure that will be here soon.

[iainhouse]

[ROADWORKS]? Not familiar

UK-speak for construction. See here for details. It's a scheme we've been using successfully for over a year now. When edits are done to the map to account for construction, all the details are posted to a Roadworks sub-forum so that we can keep track of the what's going on and the details are available to all editors.

One of the most useful features of the process is that we place a UR at the construction site that starts with the string "[ROADWORKS]" and includes a hyperlink to the relevant forum topic. Not only does it make it obvious why the UR is there, but URO+ can then have specific filters for these URs. Now, with the cone overlay, it looks fantastic.

The attachment cone UR.jpg is no longer available

[iainhouse]

It also introduces optional custom markers for URs tagged as roadworks, as requested by iainhouse

Thank you

Whilst we wait, interminably, for Waze to provide editor notes, this is a great step in the right direction.

[iainhouse]

A request please. In the same way URO+ can overlay it's own conversation markers over the Waze supplied ones, would it be possible to provide an overlay for the actual UR marker where the UR begins with the "[ROADWORKS]" marker? Perhaps something with a cone in the marker.

In that way, roadworks markers would be more obvious in the editor when reviewing your area.

[iainhouse]

BTW, URO seems to be loading very reliably the past few days. I wonder if there wasn't some sort of backend change that happened ...

If you're on the latest version:

1.37 . . . . . reduces the script startup time...

It's certainly been working reliably for me since then.

[iainhouse]

Bloody hell man - I don't even have time to post that it isn't working and you've fixed it already!

This is the shortest post I've ever seen you respond

Can't help it - I do go on, don't I.

[iainhouse]

Bloody hell man - I don't even have time to post that it isn't working and you've fixed it already!

[iainhouse]

A minor change request - nothing urgent.

When a UR description contains a web link, the script conveniently replaces it with the word "here" which is a clickable link. We're using that feature for the new roadworks procedure we're trialling at the moment.

What I've just noticed is that the shortening to "here" only happens if the URL starts with "http". When I create a UR with an "https" link, the address appears in full. Mind you, I'm assuming this is a function of the script. It is possible that it's something being done by the mechanism for adding URs from the livemap.

[iainhouse]

Damn, that's fast!

Of course, I heard the notification of your post arriving, but I ignored it because I was working out how to modify the script myself! I'll throw that mod away now. it didn't have a nice checkbox anyway.

[iainhouse]

A request for a minor functionality change.

When filtering URs including/excluding a particular string, could that be done case-insensitively?

We've got a few URs posted in the South London area for roadworks, but the work "roadworks" appears in a mixture of cases, so it's not so easy to filter them.