Is there any way to get the left/center/right lane speed if there is a HOV/HOT/Express/etc lane? This way you differentiate the slower moving traffic from the speedier “special” lanes.
The speed for those segments will be returned if the route takes those segments.
Is there a way the script can show if it is returned data is from these special lanes on road segments with lane-segregated data?
For example, this segment has 15m/7d speed data for the general purpose lanes PLUS 15m/7d speed data for the left HOV lane. How do I know which RS is returning?
Update released - 2017.11.10.001
Route Speeds should now recover when changing the WME unit and when switching back from Event Mode.
Update released - 2017.11.15.001 (MapOMatic fork)
New features (thanks to tonestertm, who did all the work):
- Added “Avoid Difficult Turns” option
- Added a checkbox and functionality to place results in Livemap’s natural sort order, to help with troubleshooting around penalties.
- Note that when Routing Order is checked, the Try More option is ignored, to better approximate Livemap results
1 Like
Awesome! This is the same version JustinS83 updated a few days ago, correct?
Sent from my iPhone using Tapatalk
cool beans.
thanks.
That’s correct.
Hi, Guys:
This is a note for future script development, The script doesn’t work when used in the US Territories, you got an “Internal Error” (red text) at the very bottom of the script area in the left panel. I made a test by moving to the Miami Area and to another caribbean island and the script worked fine, so I’m discarding configuration issues.
(Maybe this is a Waze issue and not script issue. US Territories are located in the North America Server)
Regards
Sometimes we get along well enough that we can collaborate :lol:
1 Like
I’m posting to see if this is a bug in route speeds or if some other thing is going on here.
The problem:
Waze appears to be routing around a traffic signal (signal avoidance) and that’s no surprise. What is new is that I had route speeds selected to “shortest” vice “fastest” and route speeds still selected the longer (SA) route.
The bonus phenomenon:
This video shows how sensitive route speeds is to a very small change in the start (or “A”) position in route speeds.
https://content.screencast.com/users/sawicki/folders/Snagit/media/9308193c-df39-4044-8b96-688eef25daa0/12.02.2017-13.27.GIF
A slight movement of the start position causes route speeds with “shortest” selected to go from what makes sense, ie shortest route, to the longer route which is signal avoidance.
The permalink is https://www.waze.com/en-US/editor/?env=usa&lon=-83.64084&lat=34.15140&zoom=6&segments=74747491
Is it possible to add the “Avoid Ferries” setting in route speeds?
Ramblinwreck -
Given that Waze recently removed Shortest as an option in the app, I’d first wonder if it’s even still supported in the routing server. I can’t seem to watch that video where I am, at the moment, can you re-test and see if it’s maybe selecting for time, rather than distance? I’ll do some checking when I’m back at a PC.
Edit- Shortest IS still working… still testing for that anomaly.
voludu -
Avoid Ferries should be do-able. I’ll look in to getting that added.
Disclaimer: I’m not really a dev, I just play one on TV 
Hello, it is now possible Junction Boxes to generate u-turns. It would be very helpful if the script can avoid U-turns, generated by Junction Boxes. Thank you for the script.
As strange as it sounds, I can use the script everywhere outside of my editing area while other users abroad have no problem using the script in the US territories.
Next test is to find another local editor to try the script to see if it works or not. Last step…resignation.
Is there any possibility of adding HOV / passes? Now that such routes are possible in the app, it would be good to be able to test them.
voludu - HOV routing is in development. (shortly!)
Cefin - a few of us have successfully tested Route Speeds in Puerto Rico. Are you sure you’re up to date with the latest version (2017.11.15.001)? If you are, please DM me: I’d like to try an experiment if you’re still stuck.
WazingArch - RouteSpeeds depends on the same engine that finds routes in the app and in Livemap. If a turn is defined as a U-turn in the routing algorithm, it will be avoided or allowed by the setting of the switch. BUT, be aware that setting a prompt is not necessarily the same as setting a U-turn in routing. If Waze defines the JB U-turn as a U-turn in the routing algorithm, then it should be usable or avoidable by Route Speeds, but the script does not do any U-turn detection of its own.
The experiment worked!
Now I can use the script not only in Puerto Rico and US Virgin Islands but in all US Territories.
Many Thanks Tony
Hey Guys,
I can’t get the script to work, probably doing something wrong.
I installed through tampermonkey, made sure it’s enabled.
What are the steps to use it?
Thanks!
Make sure you have the forked version installed (the original author stepped away from Waze): https://greasyfork.org/en/scripts/26091-wme-route-speeds-mapomatic-fork
Once installed it will insert a “Route Speeds” tab in the left panel.
Select the tab to “enable” the script.
Next select one segment then ctrl+click to select another segment and the script will pick up the two segments selected and process them. You will also get an A and B marker that you can move around to fine tune the routing locations.
Depending on your settings in the script’s tab, it will either show routing time through the segment or the average speed over the segment.