[Script] WME Color Highlights - 2.33 Sept 2020

[ehcool68]

Thanks for all your efforts with this script -- it is really great!

Recently I've been running into a recurring issue that seems to be coming from Color Highlights

Code: Select all

VM21548:751 Uncaught TypeError: Cannot read property 'attributes' of undefined
    at highlightBadNodes (eval at <anonymous> (:2:398), <anonymous>:751:28)

https://drive.google.com/file/d/0B7tnwIeX4x20RzRMQUM4OEs3T1U/view?usp=sharing

I'm not able to recreate it on demand, but it does seem to occur pretty regularly on some roads. In this instance, it occurred when I deleted an unneeded node, creating this segment:

https://www.waze.com/editor/?env=row&lon=73.38296&lat=25.59934&zoom=5&segments=334088313

The error repeats until I de-select the segment or scroll it out of the active window. It generally does not reappear when I re-select that same segment. I am running ver 2.22 of Color Highlights and the current version of Chrome on Windows 10.

[elle-emme]

With regards to the AM-only advanced options - specifically, the filter by editor option...is it possible to have that option available to everyone to review only their own work? I, like I'm sure most editors, made stupid overenthusiastic n00b mistakes that I'd like to clean up, and having the ability to highlight all my work would certainly make that faster.

Just a thought.

[elljay23]

It was also useful when someone reported that Waze sent them by an unusual route - you could see if the average speed for a segment was screwy it might be worth recreating the segment.

[enhket]

Thanks Tim.

[enhket]

Tim,

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

image.png

(97.05 KiB) Downloaded 1669 times

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?

[erickdeoliveiraleal]

Can you add a color to elevation different from 'solo' ?

[Ericular]

Chrome 27 went stable today, and I can also confirm that 1.6.2 did not work. 1.6.4 beta works fine though. Thanks for the link!

[Fabianotkd]

Hi,
with new speed limit reports could be usefull a "filter by SP" exactly as the filter by city with the invert check box.
Verifing city speed limits, we can find wrong speed limits.
Also out of cities we can check if all segments are with right SL...
What about this new function?

[Fabianotkd]

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?

There is no similar combination in any other tool but, at least for me, it would be very important to have an adequate level of lock in my area.

Would not it be useful for you too?

[Fabianotkd]

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.

You're right.
I would explain what I mean because that feautures are present in Toolbox but not in combination.
Informatically I mean:
(manual lock <= automatic lock) OR (lock <= lock value).

This could highlight also segments at lock level 1 with automatic lock 1.
In toolbox hasn't this combination.