[Script] Highlights for Segments & Landmarks - v1.5 Nov 16

[Timbones]

I seem to have run into an issue with the city highlighting. I select a city from the drop down, and not all the roads that are in that city get highlighted.
[...]

That is very odd. I tried it myself, but I could not replicate it. It could be because the Road Data from Waze is incomplete.
Do you get any errors in the Error Console? (Ctrl+Shift+J)

Edit: Send the details via PM...

[Timbones]

Thing is, do levels actually have any purpose? They might be used for rendering overlapping roads in the client, but they don't influence routing. When there's a fat purple line on top of the map, the levels aren't visible anyway.

Hiding levels won't be possible, as the tiles are drawn on the server.

via mobile

[Timbones]

Is there any way of running this UserScript via Tampermonkey (v2.6.2767)?

I'm not familiar with Tampermonkey but I shall look into it. Are there any errors is the console?

I did consider integrating a version check into my script, but wasn't sure if it would be worthwhile.

via mobile

[Timbones]

Gas stations are turning red after loading the script and activating "Highlight Landmarks".

It's a feature. Shows the station details are incomplete.

via mobile

[Timbones]

I'm wondering if there's a better way to see these errors than to select each node individually. ... It would be cool if I could see all the bad junctions at a glance.

The script used to display all the nodes with warnings, but it made the map look like it had bad cases of the measles. This encouraged editors to 'fix' every single node that they could see, without actually benefiting the map. This could actually cause more harm than good, as properly disallowed turns could easily get reset by a careless editor.

Generally, the Waze map works just fine with the existence of soft-turns and reverse-connectivity. The script was changed to only show the state of a selected turn, and it is intended to be used when there is a problem with routing that needs to be diagnosed.

[Timbones]

Here's yet another new version for you!

v1.4.1
- checkbox for showing highlighted turns when selecting a node or segment
- display turn warnings in edit panel for selected segment
- display average speed for selected segments (code by bgodette)
- suppress no name highlights from roundabouts and non-Streets
- suppress highlights from unterminated roads which are very short (<10m)
- fixed many bugs for improved robustness and compatibility

> http://userscripts.org/scripts/show/141050

Updated: be sure to get the latest version from the link above

[Timbones]

I regret to report a possible problem.

I installed v1.4 last night and have been working on a basemapped area. I began to notice that I wasn't seeing any selfcons (red highlights) despite situations where I would expect them. I downgraded to v1.3 and found one almost immediately where v1.4 didn't.

Thanks Iain, I'll take a look...

via mobile

[Timbones]

However, I assume that in amongst the bugfixes, was one that "fixed" erroneously named roundabouts not to show as yellow/orange, which, as was briefly discussed in the thread recently, was very handy - particularly in my neck of the woods!

I'm considering adding a separate highlight for roundabouts which are named or two-way, but haven't quite settled on how to display it...

[Timbones]

I installed v1.4 last night and have been working on a basemapped area. I began to notice that I wasn't seeing any selfcons (red highlights) despite situations where I would expect them. I downgraded to v1.3 and found one almost immediately where v1.4 didn't.

Well spotted! I knew I should have kept this in beta testing for longer...

Anyway, this issue fixed in v1.4.1

[Timbones]

Still no highlights on those nodes I quoted before.

Looks like a bug specific to Firefox. Works fine in Chrome. I'll see what I can do...