I don’t know what the problem was, but I’ve republished the script and it’s fine now.
Hi,
I got the link “Show routes between these two segments” now and it works !
Thanks, Herve
Updated script for Firefox uploaded to UserScripts.org.
New version will appear in Chrome Web Store shortly (auto-update)
Changes:
- made to work in new WME version (please report issues)
- increase visibility of the primary route, with less emphasis on alternatives
Very strange routing results between two segments of I-10 in Houston (almost any two segments, this is just an example)
https://www.waze.com/editor/?zoom=5&lat=29.78258&lon=-95.46957&mapUpdateRequest=3369696&env=usa&layers=1925&segments=47539580,61767826
Why does it think we are on Katy tollway? The segments selected are NOT on the tollway.
I even get similar results with CONSECUTIVE segments of I10.
From user reports, it is clear that WAZE seems to think the drivers on I10 are on the Katy Tollway TOO, some of the time!
Question about this extension: how are the ‘starting coordinates’ and ‘ending coordinates’ for the route determined?
Question about the routing engine: how does the routing engine determine, from the coordinates, exactly WHICH segment the ‘driver’ is currently located on?
Note: I have seen similar results in livemap, even when the ‘dropped pins’ clearly indicate starting and ending points on I10, the routes produced start on Katy and end on Katy.
This would only be an annoyance for map editors if it didn’t seem to be effecting actual routing!
Waze is not supposed to route to a location on a freeway. The problem is that Livemap also seems to take this into consideration when setting the origin point as well as the destination point. To test freeway routes, I generally have to put the start point on an onramp going the direction I want, otherwise Livemap will often select some other road that’s near the freeway to put me on and that will mess up my tests.
In actual life, your route could start on a freeway (passenger selecting route for you, or you are pulled off to the side for some reason), even if Waze won’t route to a destination that’s on the freeway. It would make testing a lot easier if Livemap would allow the origin to be on the freeway.
Does your script really needs to have access to all URLs / history?
+1
I just seconded this for WME Toolbox as well. I like that people are making noise about this - Chrome extensions should be properly scoped. thank you!
Hi there!
Is there any other source of download since Userscripts.org has not been working lately?
Thanx
Use a link with the port 8080
neither port :80 nor :8080 work for me.
If you are using Google Chrome Browser you can get it through the Chrome Web Store. It will then also update automatically when a version is published.
I’ve added an alternative download for Firefox while UserScripts is unavailable.
Since it appears that UserScripts.org probably won’t be returning to a usable state anytime soon are there any plans on moving the script over to greasyfork.org or some other site?
There’s an alternative download link above.
I was having some trouble which the menu “Show routes” wasn’t appearing.
For those who’s facing this issue, clean your cache. Worked for me.
Awesome Tool for saving time swapping screens.
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!
Confirmed, very strange, it should follow livemap ;d Please look into it.
@Timbones, is there any solution planned in the nearby future? 
New version (1.1) uploaded to Greasyfork:
- Added support for U-turns (default = on)
- Can now avoid Tolls, Freeways and Dirt Trails (default = off)
- Also moved turn icons on top of all other layers (not well tested)
Please test and let me know if it works well for you. I’ll build a Chrome version if it’s okay.
:ugeek:
1 Like
Interesting. Thanks for the new features.
Not sure if it is a bug, but after displaying a route, when I clicked try to click on any segment after the route has displayed, the route goes away but I can’t select segments.
Need to do an F5 reload before mouse-over will show ‘about to select’ any segment or click actually select.
Win7, up to date, chrome platform, tampermonkey. I have not tried disabling my other extensions to see if the problem goes away.