Waze forum

Okay, I really think I've got it now. Tested in Firefox, Chrome and Tampermonkey.

v1.4.2 - http://userscripts.org/scripts/show/141050

jasonh300 wrote:I don't know what version I'm running, but if I see 30 Oct 2012 in the title, I'll know I have to upgrade.

I'll try, but there's not much room in the title for anything else.

The version is shown at the top of the highlight options, and the title links directly to the page on userscripts. It shouldn't take much effort to manually check for a new version now and then.

I did consider adding an automatic check, but it seems a little late in the development life cycle. I'm not expecting many updates from this point on...

(my other script hasn't changed since March)

via mobile

Rename it to wme-highlights.user.js and try again. Probably worth removing old versions too.

via mobile

TheDane wrote:+1 on the suggestion from skbun about making it possible to see all problems in an area using a colour coding for all segments that have issues.

This was how it worked in an earlier version but it showed an aweful lot of problems, most of which don't actually need fixing. I felt that showing all nodes with soft-turns would encourage editors to QW all of them, which adds little value to the map and increases the chance of turns being set incorrectly. Therefore, I took the decision to only show them for one node/segment at a time, for when a particular routing issue needs to be diagnosed.

AlanOfTheBerg wrote:I saw a post earlier in thread about not seeing the segment/junction warning highlights. The properties toolbox says "x soft turns, y u-turns" etc., but the segments don't highlight.

This was fixed in v1.4.2. Do you have the latest?

skbun wrote:If I touch any given segment, and then click 'Save' in WME, any segment which I had changed comes up with a wacky speed result. It doesn't matter whether I have any node (or the node in question) highlighted when I do click save; this result persists until I reload the page.

This is a known bug in the WME code, for which I may include a fix for in future versions.
Workaround for now is to reload the editor, or ignore the crazy speeds.

I'm running the exact same version of Chrome, also on Windows 7. Works okay for me.

Can you post a permalink that shows this problem?

Did you enable the advanced option [ ] Turn Warnings for Selected Nodes?

svx-biker wrote:Just found that it's not related to the server but rather to the user. Is this intentional, i.e. a level(0) user has fewer options?

Yes, this is correct. The Advanced Options only appear for Area Managers.

mike-bronner wrote:would it be possible to add a highlight selector for states? I am editing in one of those states that have been thoroughly mixed up with a neighboring state, and would love to highlight out all the errant state segments.

Maybe. Problem is, we don't have 'states' in my country (rest of the world), despite us begging Waze for 3 years.

Can you post some example permalinks?

I have made a beta version that appends the state and/or country when there are more than 1 defined in the model. It works quite will with skbun's example of Federal Way above. I've also tested it on international server.

> WME Colour Highlights Beta - v1.4.3

Let me know if this works for you guys...

PS: I also notice that each state object has a geometry. Any ideas what we can do with it?

One question would be: where do the state geometries come from (Tiger?) and are they accurate?

City objects do not have geometry.

via mobile