[Script] Livemap Navigation Browser Addon [Deprecated]

[AlanOfTheBerg]

The LiveMap is well-known for giving different instructions than the client, so I'm not understanding why this is being called out because of this script now. The script doesn't do anything different than access the routing given to the livemap and doesn't make a special call to the routing server.

[AlanOfTheBerg]

Tim, after using the Close button, then doing another navigation, the side panel disappeared for me, sliding the whole map to the left. No navigation information and no standard waze scrolling info either. The map was a little confused then with mouse click location.

This is repeatable. Chrome on Win.

[AlanOfTheBerg]

Funny you should ask... http://www.waze.com/wiki/index.php/Comm ... _and_Tools

[AlanOfTheBerg]

Also linked from within http://www.waze.com/wiki/index.php/Map_ ... _and_Hints

[AlanOfTheBerg]

Is it possible to select alternative route?

There is no functionality this extension adds to the LiveMap. If the routing server returns multiple routes, the LiveMap will show them and this extension will also show the instructions for multiple routes.

For example: http://www.waze.com/livemap/?zoom=13&la ... g=10232581

[AlanOfTheBerg]

If the routing server returns multiple routes, the LiveMap will show them and this extension will also show the instructions for multiple routes.

Waze has a self-imposed limit of 2 routes that it will show. I haven't tried to influence it, but it could theoretically be persuaded to return more than 2 routes. Maybe.

There are max. 3 routes on client. Can we add intermediate point as Google map?

Unless someone builds a new livemap which accept 3 routes, this won't happen. The code isn't making special calls to the routing server but just using the client-side data already present when the data comes back from the call done by the livemap code itself. It seems you still think that the extension code is doing something special in interacting with the routing servers. It isn't. It's just using data already present in the data in your browser when the livemap requests a route. I don't think it would be a trivial matter to override the functionality of the livemap code itself to get 3 routes back and then somehow get the livemap to display 3 routes.

Intermediate route points I think would also be a huge coding undertaking. The routing server doesn't have this capability already, so this would have to be coded 100% on the client, making multiple calls to the routing server for A->B routed, then B->C route.

[AlanOfTheBerg]

Does the navigation data returned for the route contain speed camera information?

I don't have any speed cameras in my area, so I checked Red Light cams, which should be treated the same. I did not see any evidence of these in the XML or JSON version of the route.

[AlanOfTheBerg]

The filename must end in "user.js" for Chrome to accept it.

[AlanOfTheBerg]

Right, and if you save another version of the file, Chrome download sees the extension as .js instead of .user.js and makes it .user(1).js.

Yes. I just wanted to make sure it was clear what the filename should end with in case itwasn't clear. It's a bit picky of Chrome, IMO.

[AlanOfTheBerg]

Would it be possible to apply a similar tool in the editor?

This is something which has been brought up in other threads. In short, unless the functionality is provided by Waze, we cannot build this on top of the editor map, at least not without a LOT of coding work. And even then, only roads selectable in the current view would work.

The code from this tool only uses the information which comes from the routing servers. The routing servers do not use the edit map to make routes. There is no similar functionality on the edit map.

Waze has told us before that they have this on a long-term roadmap. I would not expect anything official for many months, maybe a year or more.