Tue Nov 25, 2014 6:35 pm
Tue Nov 25, 2014 6:49 pm
Fri Oct 12, 2018 1:43 pm
Mon Jul 11, 2016 4:30 am
Fri Mar 08, 2019 2:37 pm
Wed Jan 11, 2017 1:58 pm
uscwaller wrote:Bug....it calculates the time of the route, but does not highlight the route
Wed Jan 18, 2017 2:13 pm
Olestas wrote:MapOMatic / JustinS83
the script is not doing anything on WME language interfaces other than English.. can you fix this?
For example Latvian or Russian interfaces
Spams console with error
Uncaught TypeError: Cannot read property 'layers' of undefined
at loopWMERouteSpeeds (eval at <anonymous> (:2:297), <anonymous>:1846:23)
loopWMERouteSpeeds @ VM303:1846
I18n.translations[I18n.currentLocale()].layers.name["__DrawRouteSpeeds1"] = "Route Speeds";
Wed Jan 18, 2017 2:58 pm
EDIT: Oops, sorry for the double post. Seems I was a bit too slow.
Thu Jan 19, 2017 1:01 pm
hmarian wrote:MapOMatic and others...
Is there a minimum distance between the two selected segments, in order to receive more than one route?
I get 2 or more route when the segments are far from one another and only one, when they are close, although there is more than one valid route.
Thu Jan 19, 2017 4:06 pm
hmarian wrote:JustinS83 wrote:This script is merely using the routing engine to determine the routes. Just like if you were to use livemap or the app, if your start and end are too close the routing engine will only have one route that it determines is the best.
I appreciate the answer.
If this is the case, could you or someone else explain the context of 4th and 5th "Alternative routes", which are not available in LiveMap (max 3 are shown).
The same question goes to the "try more" option. How is this functioning.