[Script] WME Color Highlights - 2.33 Sept 2020

[Timbones]

The current beta can be found on Chrome Store: WME Colour Highlights v1.7.3.
No significant changes since v1.7.1, just testing that it works from the store.

Don't forget to uninstall the old version!

Being in the store does bring a few advantages:

• One click installation
• Synchronised across devices
• Automatic upgrades

I'll add in my other scripts when I get the chance...

[Timbones]

The highly useful feature for highlighting UK road names which do not conform to standards (e.g. Road instead of Rd) needs to be updated for the recent changes to ramp naming standards.

The latest version ignores bad names on ramps.

[Timbones]

* Updated Chrome version (v1.7.4) so that it will work with non-English languages.

[Timbones]

I've uploaded the beta version of this script to UserScripts.org for all Firefox Users. Version number upped to v1.7.4.
Chrome users should uninstall the old script (v1.7.1 or older) and get the new one from Chrome Web Store (v1.7.4).

Links in the first post (and in the Wiki) have been updated.

[Timbones]

Three questions:

1) Can I get some details on "Turn Warnings for Selected Nodes*"? I'd like an explanation of how it works, why it has an asterisk, and how it compares to the similar functionality of the Toolbox.

2) Why is there an asterisk on the Unterminated Roads option?

Hover over an option with asterisk to get explanatory tooltip.

Select a node with warnings, and you'll see a link to a page that explains what they mean.

[Timbones]

Updated script for Firefox uploaded to UserScripts.org.
New version will appear in Chrome Web Store shortly (auto-update)

Changes:
- made to work in new WME version (please report issues)
- traffic lock highlight option now available in main WME, but is not available in all countries yet

[Timbones]

In order to detect the zones with problems, is there any way you can add a color for this kind of issue?

I'll consider it, though it might be a rule that would be best added to WME Validator.

[Timbones]

Looks like it is time for an update for segment speed data.

I just got on my main computer and saw the issue for Colour Highlights on every segment. Toolbox's FwdSpeed and RevSpeed were also 0 for every segment. Once the script writers get wind of the issue, a fix should be possible using averageSpeed. I currently cannot tell if that is useful for both directions though...because I'm a SQL developer

I see that fwdSpeed and revSpeed have both been removed from the segment attributes, presumably because they deemed to be not useful by HQ. I don't see any 'averageSpeed' attribute though, or anything else that indicates speed. I shall have to remove this feature.

[Timbones]

Average speed may have been a useful indicator of problems, or it may have just been a coincidence that it went wonky some of the time. Either way, it's gone from the data, and its relevance is now moot.

[Timbones]

Updated! Available from UserScripts now, and will shortly be available on Chrome webstore.

• Remove extra speed data for selected segments, after Waze dropped it from the model
• Fixed behaviour in Beta editor, wrt. house numbering (no Landmark highlights if not available)

I'll look at maybe supporting "Places" in the future once the feature has matured a bit.