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

I've been having intermittent issues on Firefox for a while now seeing the navigation path and instruction overlay in WME. Note that the list of instructions are displayed fine on the left panel - I'm speaking of the purple line, arrows, and instructions on the map itself. Sometimes the route checker layer doesn't seem to be on top. Through some quick WME layer toggling and/or scrolling around during slow page loads, I sometimes catch a glimpse of it. So it seems like it's being drawn, but it's underneath the current view. This same layer toggling (any layer, but mostly the satellite layer it seems) can sometimes correct the issue, but usually several page refreshes are necessary until it (seemingly) randomly starts working again.

Seen on FF 45 and 46 as recent as today.
WME Route Checker - v1.23

This line

Code:

W.map.addLayer(WMERC_lineLayer_route)

is causing a TypeError in the console:

Code:

userscript.html?name=WME%20Route%20Checker.user.js&id=1bce74b7-4cb4-461f-8270-59aa6d7c4004:857 Uncaught TypeError: Cannot read property 'addLayer' of undefined
    at initialiseRouteChecker (userscript.html?name=WME%20Route%20Checker.user.js&id=1bce74b7-4cb4-461f-8270-59aa6d7c4004:857)

This line

Code:

W.map.addLayer(WMERC_lineLayer_route)

is causing a TypeError in the console:

Code:

userscript.html?name=WME%20Route%20Checker.user.js&id=1bce74b7-4cb4-461f-8270-59aa6d7c4004:857 Uncaught TypeError: Cannot read property 'addLayer' of undefined
    at initialiseRouteChecker (userscript.html?name=WME%20Route%20Checker.user.js&id=1bce74b7-4cb4-461f-8270-59aa6d7c4004:857)

I've replaced the bootstrap section in my local copy with these lines, now it always loads correctly. FYI

Code:

function bootstrap() {
    if (W && W.map && W.model && W.selectionManager) {
        console.log('"WME Route Checker: init route checker...');
        initialiseRouteChecker();
    } else {
        console.log('"WME Route Checker: Bootstrap failed. Retrying...');
        setTimeout(() => {
            bootstrap();
        }, 1000);
    }
}

bootstrap();


Awesome...

One question, if it's based off the livemap data, why won't it work in WME Beta (i.e. if the routing is coming from the livemap, why does it matter what editor you are using)?

One question, if it's based off the livemap data, why won't it work in WME Beta (i.e. if the routing is coming from the livemap, why does it matter what editor you are using)?

It's because the beta editor is on a separate domain, and browsers don't like you loading data from another domain for security reasons. I've asked Waze for some help with the matter, but there's a lot going on with the websites at the moment, so we'll have to see...

I get it, but it's still in the same root domain (they are all *.waze.com)...

I have a few wierd routings, although on the livemap it works correct.

The livemap routes are now implementing the uturn function, but the route checker script is not using those same uturns.
Could you have a look at that please?

Thanks!

The livemap routes are now implementing the uturn function, but the route checker script is not using those same uturns.
Could you have a look at that please?
Thanks!

@Timbones, is there any solution planned in the nearby future?

^^^ That would be nice. I still have to use the alt shift R quick refresh, before i can select other segments to try different route info.

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!

The Chrome extension is not longer supported as mentioned a few posts above.