Used this a couple of times a few minutes ago and this looks like it will help out a lot with testing routes. Great job with this script and keep up the good work. Really thankful for all that all the script writers do to help us people that can't spell "computer" out with editing.


Sent from my iPhone using Tapatalk

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

cotero2002 wrote: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

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.

tonestertm wrote: 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.

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

Hi

Today I received a strange error.

Is this a known issue?

CHROME 47, WME - prod

How many routes for the same start and end points do you get on live map?

Yes, this script used the same routes as live map, I just wanted to make sure something hadn't changed there that was causing only one route to show. Not exactly sure, but it could be that Waze calculates the other routes are significantly slower than the fastest so it just decides that there's only one way to get there. Could also be that is short enough that it only thinks one is appropriate. Someone else probably knows more info than me and could give a more detailed answer

doctorkb wrote:Looks awesome!

One feature suggestion (that may be beyond the reasonable request -- not sure) is some way to compare two routes. I.e. be able to say "go from A to B, via C" so that we can see why a different route (perhaps the way our instinct would have taken us) wasn't chosen.

+1. If there's an alternate specified in LiveMap, display that too. Also, crosstimes based on time of day?

Szata76 wrote:Same segment on same direction displays different speed depending on the start and endpoint. Of course the segment is in the middle of the route not at the ends.

That would be due to the routing request returned from Waze and not the script per se.

CBenson wrote:I'm not understanding this (and would like to). The speed data isn't delivered with the route is it?

Segment length and crosstime are, so it is easy enough to derive speed. This is available in the LiveMap now but not exposed in the user interface.

It's different than the "average speed" we used to have in WMECH, which was actually using segment attributes from the editor and not a LiveMap routing request.