Any maybe use the yellow color for soft u-turns that other soft turns are highlighted with?

Strange, I have no problem under Firefox.
Highlights works fine for me.

I have the script failing to highlight any PLRs.

Appreciate all the hard work you put into this.

Love the script, but I keep seeing this in the javascript console and it tends to slow down almost to a grind in cities with alot of roads...

http://s20.postimg.org/bzvmx1wu1/sshot_19.jpg

How about show/hide filter by landmark type ?

zannax wrote:Hi, chrome users can install and use your script with TamperMonkey addon.
To install scripts with Tampermonkey just click on button install.
One of feature of TM si auto update of script

TamperMoney does not always work with userscripts.
Although the auto update is a great feature it is quite useless because most of waze user script do not run properly in TamperMonkey.

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?

3) Could we get an option to have "no name highlighting" only apply to specific road types? It is typical for parking lot roads, private roads, and often ramps and service roads to not have a name, and the highlighting only makes it busy. Usually, I want it for regular roads -- streets, primary streets, minor highways, major highways, and freeways. Sometimes ramps and service roads.

Toolbox and highlighter are complements. I use the highlighter to visually spot these things quickly. The toolbox requires a bunch more steps, and the sort can be slow on a largish, zoomed-out view.

SuperDave1426 wrote:

enhket wrote:Tim,

A few people reported that whenever a segment got wrong speed data, it will fail to route properly. For example, here:

image.png

The segment goes from B-A, but no speed is saved for that direction. It is saved for A-B as you can see. Creating the segment again usually fixes the problem (sometimes we have to replace a few more segments).

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

I've seen things like that from time to time, too. But I'm wondering - what exactly can we do about it if we find one? Do we have the ability to adjust the average speed or reset it (without deleting the segment and recreating)?

If the reversed direction is accurate, I suppose you could preserve the speed data by disconnecting the end and reconnecting to swapped positions. That would also preserve house numbers, though they might be reversed and need monkeying with.

If the data is completely bogus, you have to either delete it wor wait for it to get updated with legit data (which may never happen if some corrupts database entry is what is causing the bad speed data to begin with - so, yeah, delete it and recreate, but try to recreate house numbers if its is fully bogus).