[Script] WME Route Checker - v1.40 Sep 2020

[Timbones]

Updated today to unbreak new WME. v1.27.

[Timbones]

Here it stopped working, for anyone else?

v1.29 will be available from Chrome Web Store shortly...

[Timbones]

I've just uploaded version v1.32 to Greasyfork with some minor fixes, and a new feature that displays when a route goes through a restricted zone (like Clear Air or ZTL) or through a Toll.

Note: The Chrome extension is no longer supported. Use Tampermonkey instead.

Enjoy!

[Timbones]

What is considered a Natural Route?

No idea, it's just what Waze calls it in the data that it sends back from the routing server.

[Timbones]

v1.40 of WME Route Checker brings a new feature: Lane Guidance!

The route will now display the lanes as they are shown to the user in the app, including any heuristics that may be applied on H and # style junctions. This includes straight-ahead lanes which are displayed* or announced where there's otherwise no instructions. (*'View only' override will be marked with eye emoji)

Code: Select all

keep right onto Station Rise
              |   ┆ ↑ |
turn right onto Station Ave
              |   ┆ ↱ |
keep left onto Museum St
              | ↰ ┆   |

Also shown on the map in concise form, like |↰↰..| for 2 of 4 lanes.

There may be a few undiscovered bugs hiding in this version, so if you see something that doesn't look right, please do get in touch.

[Twister-UK]

There's still the issue that when you have a route showing, you cannot deselect one of the segments to select another. You can only click to deselect all of them, and start again. This is because the route layer is now shown on top of the segment selection layer, and I can't figure out a work around.

Any reason why the obvious solution - adding a "pointer-events:none" style to the layer container div - isn't suitable? A quick play around with this version of the script suggests there's no need for it to capture any mouse events on the route layer, so letting them all fall through to the underlying WME layers seems safe enough.

[Twister-UK]

Feature Request:

It'd be handy to have an indication of when the most recent edit was done along the routes being displayed, to save us having to click on each segment manually to see if there've been any changes made since the UR was submitted and which might then account for the WMERC results failing to confirm what the UR reporter is complaining about...

[voludu2]

I am having a problem with a route -- route checker seems to be picking the wrong destination point/segment. Perhaps this is because another segment crosses at the midpoint of the selected segment. Is it possible to drag the destination point a little further along the segment?

https://www.waze.com/editor/?env=usa&lo ... 1,83162659

The route is like this:
https://www.waze.com/livemap?lon=-75.91 ... 9862302085

But it should be like this:

https://www.waze.com/livemap?lon=-75.90 ... 62&zoom=15


Thanks for this really amazing script. It has allowed me to find all kinds of things that need to be fixed.

[voludu2]

iainhouse -- thanks. That's the workaround I used.
PesachZ -- So obvious -- once you point it out. Doesn't have to junction anything, be saved, or even be in ones editing area. Only there to generate an endpoint. Thanks.

[WazingArch]

I've noticed difference in road instructions (prompts) produced by the script and Live Map at roundabouts with certain configuration. Script produces different than Live Map instructions if entering and exiting segments are connected to one node on roundabout.
You can check this on WME here.
Screenshot form WME: http://prntscr.com/gb7z9n
Screenshot from Live Map: http://prntscr.com/gb81mm