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

[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]

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]

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]

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]

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]

Bug(?) in chrome, windows: hitting Q when a node is selected automatically turns off the yellow (soft turn) but not the magenta (reverse connectivity) highlights. If I hover over the magenta after hitting Q, it disappears, however.

I attempted to fix this by binding a reset function to the Q key. Unfortunately, it doesn't work in Chrome. It does work in Firefox though.

[Timbones]

PS: the colour key, only appears when a node is selected.

That's what I said.

I know. I'm saying that it's supposed to be like that.

BTW, I should really credit bgodette for this feature, as it's his excellent code that I used in this version

via mobile

[Timbones]

Then how can I get a RevCon error at a junction when the junction is at the 'entrance' end of a one-way street?

This means there's an enabled turn /out/ of the entrance end, even though the editor doesn't show it.

And yes: Q+W will fix revcon issues. Be careful about enabling turns that should not be.

PS: the colour key, only appears when a node is selected.

via mobile

[Timbones]

Does it auto update on Chrome? I'm still at 1.2. Do I have to uninstall then reinstall again?

No, it doesn't auto-update (though I nearly added it). Install again to get v1.3 (there's a link in the editor).

With FF14 it does not appear to do what you have described for soft turns, revcon or for highlighting the segments connected to each end of the selected segment. Everything else appears to be working. Did not try other browsers.

Hmm... I also had trouble getting it to work just now, but it did in the end. Try reloading the editor.
This might be related to the 'toolbar not enabled after login' bug that we have in Chrome.

Here's what you should see if you find a node that isn't right:

Node Highlights

node-highlights.png (20.6 KiB) Viewed 829 times

[Timbones]

What do the different colors say? I've seen yellow and pink so far..

Click on a node, and you'll see colours explained in the side...

via mobile