sketch wrote:Hey, I don't usually have cameras layer on so I hadn't noticed this before. What's the "not valid?" speed check do?

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.

The "not valid" text in the camera popup is then simply a prompt to the user that the defined speed for that camera may not be correct based on that "multiple of 10" rule. If cameras in your area are allowed to have speeds set to something other than a multiple of 10MPH, you can ignore this text.

Having spent the last couple of weeks on business trips and family holidays with no opportunity to do any coding, it comes as something of a relief to be able to dust off the editor and source code again... 3.46 introduces a couple of new features:

• Added restricted turn popup
• Provisional support for Road Closure MPs (for those beta users with access to them...)

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

3.47 introduces the following changes:

• Restricted segment popup now displays correctly when restriction has no description text
• Mutually exclusive filtering options in the URs tab are now enforced again, and are enforced for the first time in the other tabs
• UR popups now show detailed submission/closure timestamps
• Road Closure MP popups now display the correct title text

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

I was already planning to do something for the equivalent reports we're now getting over here in the UK, so once I get the framework in place for those then it shouldn't be difficult to add in support for the way they're being tagged elsewhere...

3.48 introduces the following changes:

• Uses I18n.lookup() to allow graceful fallback when selected language doesn't include a required translation string
• Added custom markers for Elgin, TrafficMaster and TrafficCast MPs
• Enabled collapsing/expanding of the places filter category lists

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

Olestas wrote:

2015-07-14 09_20_57-Waze Map Editor.png

Can options be added to set Date format to DD/MM/YYYY and Time format to 24-hour?

Note that the date and time are formatted using the .toLocaleString() function which use your current system settings to decide how the date/time should be presented, so if your system is set to DD/MM/YYYY and 24-hours (as mine is), then that's how the date/time will be presented in URO+ too.

If you don't want to/can't change your system settings, then I'll consider adding a URO-specific locale setting in a future release...

3.49 introduces the following changes:

• Date and time formatting in popups is now user-definable (within reasonable limits )
• Place popups now include links to locate the navigation point in the current or a new tab
• Selecting a "new tab" option from popups displayed in the "new" tab now causes another new tab to be opened
• Camera popups now use country-specific speed limit formatting
• KMH/MPH speed limit filters for speed cameras have been removed. New filters added for speed cameras with/without any set limit.

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

On the Places tab in the "Filter PURs by category/status:" group, try the "Ones I can't edit" filter

Thortok2000 wrote:It looks like MP's now have a flag of when the issue is outside your editable. Can we have a 'ones I can't edit' filter for MP's now too please?

The editable flag appears to be more a way to show whether *anyone* is able to edit a particular MP, and based on all the MP objects I've examined so far looks to be just a different way of telling whether a MP is open or closed, with its value copying that of attributes.open in each case.

On the other hand, the canEdit() function does provide a true/false response which does seem to take the current editable area of the user into account, so you should find something of interest in the next release...

3.50 introduces the following changes:

• Option to hide MPs outside of your editable area
• "Landmarks" changed to "Places" in the Misc tab "Disable popup for:" settings group...

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