Waze forum

I'm using it in Chrome (latest "standard" version) and with both WMECH and WME-Addons. I know that Toolbox relies on the presence of WMECH for some of it's functionality and it may need the latest beta version (1.64).

Mike-1323 wrote:For some reason version 1.6.2 and now 1.6.6 is picking up the version number from WME-Add-Ons. That is, in WME the highlights tab shows version 0.44 when the chrome://extensions/ page gives the version as 1.66. The extensions page shows WME-Add-Ons as version 0.44. Not really a problem, just a nuisance to always have that little update flag flashing in the highlights tab because it is comparing itself as 0.44 instead of the correct 1.66.

I encountered this problem around the time the Chrome update started breaking all the .js scripts. As I recall, it turned out I had 2 versions of one of the scripts installed (may not have been WMECH itself).

I suggest you double-check your extensions tab & make sure this hasn't happened.

A selfcon is an allowed turn at the end of a segment back onto the same segment - and it doesn't matter whether or not the segment is one way.

A revconn is an allowed turn from one segment to a second one-way segment, where that turn violates the direction of the second segment.

Unfortunately, whilst editors can now control u-turns, the vast majority of them that I have seen are not the work of any editor. They are, presumably created by the Waze engine having seen drivers apparently perform a u-turn at junctions in the past. Mostly (in the UK) this will be people reversing into a side-road at a junction and then going back the way they came. Whilst all these u-turns are theoretically possible, Waze should not, in most cases, be using them for routing.

I am of the strong opinion that Waze should have removed all existing u-turns from the map before changing the editor to allow us to control them manually. That way, the only u-turns left would have been ones enabled specifically by editors.

Fabianotkd wrote:Hello and excuse me..., can you insert highlight segments that have:
manual lock equal to or less than the automatic lock
or lock less than or equal to a certain value?

Both of these features are available to some extent in Toolbox.

Toolbox has a segment highlight that shows segments manually locked below, at, or above their auto level: red for segments manually below auto, green for segments manually above auto, cyan for segments at auto but manually locked.

You can also use the Toolbox Select Segments tool to select segments with a particular value.

Lenamax07 wrote:As it looks like there is a problem with the WME Colour Highlights App since short time.
It doesn't highlight anymore anything.

Best Regards
LenaMax07

P.S. A great thank you for that fantastic tool!

Just had an update to WME and Color Highlights has stopped working - Coincidence, I think not?!?

CrackedLCD wrote:Welp, I'm at a loss here. After installing 1.6.2 the script doesn't work anymore. Nothing highlights, and there are no options under the dropdowns for cities or the purple highlight type. I uninstalled and reinstalled the script to no avail. Am I the only one having this issue? Haven't seen any other posts on this, or how to fix it.

You may have to disable NoScript if you have it running, it may prevent running the script (or parts of it). Also check what options you have enabled, of course.

You can get them all at http://userscripts.org/scripts/versions/141050 - but they're not named with the version number in that list.

Once the street is loaded you can check But it loads it into the objects per street, once you open the editor.

You can gather the info by calling:
https://world.waze.com/Descartes-live/a ... 7,89150743
(Multiple segment IDs comma seperated).

Perhaps OyyoDams has a better solution, though, as my solution may be kind-of resource intensive if called for multiple segments.

AlanOfTheBerg wrote:

tonestertm wrote:I don't know if it's possible, but I'd love to have CH indicate segments stacked on top of one another, especially when they're both set at the same Road Level.

I think I've asked for this before too. I'd love to see both a "conflict" checker (which is pretty advanced as the code must figure out if two segments overlap: not a trivial matter to code), and a level display: where each level is a color of the rainbow and I can scan for overlapping same colors.

It's fairly simple with some basic math, actually. I've added it to my personal version of the highlight script, two different types of checks: one which simply checks the start and end nodes of each segment and highlights those for which they overlap. This may be incorrect with segments which have sharp turns though.. so I added a second option which checks every geometry point of each segment, although this may be slow when lots of segments are loaded. It doesn't check road levels though, just indicates which segments overlap. Very useful in case you're creating a new city block and simply join various segments into a node.. you tend to forget some

And I've added many other items to the script, like unreachable segments (with no green incoming TRs), highlighting of dead end segments (also useful when creating those city blocks), highlighting of all types of roads instead of one, color picker for everything, nodes which can be removed, segments with multiple geometry points so it makes it easy to figure out which streets to straighten if needed, etc

Works wonders, just have to figure out some time to make it a crx now.. annoying chrome update.