[Script] Livemap Navigation Browser Addon [Deprecated]

[CBenson]

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.

Well, it was kind of inferred that this could be some sort of substitute for the lack of the navigation list on the client. That might trigger some expectations that the instructions would be similiar.

[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]

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.

[petervdveen]

Maybe that's because of the 3.0 version?

[robin1979]

This would be fantastic - if it returned the same instructions as my phone. Alas, it does not.

Indeed that is a problem. I should have added the caveat that the instructions may not match those on the client.

I think the route data given to the Livemap is the same as the client (but I can't be certain), so any differences will be down to how the addon interprets those instructions vs. how the client interprets them.

Also, in Paris, asterix06 noted there are some differences on the iPhone vs. Android (he's using both). They seem to be getting different routes for the same trips for some reason.

[dmcconachie]

For example, I've decided to include the 'continue on' instructions that the client wouldn't.

Found this handy for spotting naming inconsistencies already!

[Timbones]

This would be fantastic - if it returned the same instructions as my phone. Alas, it does not.

Indeed that is a problem. I should have added the caveat that the instructions may not match those on the client.

I think the route data given to the Livemap is the same as the client (but I can't be certain), so any differences will be down to how the addon interprets those instructions vs. how the client interprets them. For example, I've decided to include the 'continue on' instructions that the client wouldn't. Also, there's that ramp naming bug that doesn't appear to affect the addon. There may be other instances where the instructions differ, e.g. when there are unnamed segments.

I shall check out your example route to see if I can improve it at all with regards to handling the exit instruction.

[CBenson]

This would be fantastic - if it returned the same instructions as my phone. Alas, it does not. I'm using a Verizon Droid2 Android 2.3.3 waze 2.4.0.26. I'm incredibly frustrated by the ramp naming bug. So of course the first thing I did with the extension was to check a few ramps. They do not show the same as on my phone. For example, I used the extension to travel from US-50 westbound to I-97 N here. Great, the first ramp name is listed! But as I'm on Android version 2, I still have a navigation list on the phone. The instructions that show on the navigation list on the phone are:

Exit right to to I-97 N Baltimore
Keep right to to I-97 N Baltimore
Approaching destination.

It is great to know that there is readily available code that provides the correct instructions over ramps. I just wish it was on my phone.

Tim, great work, I really appreciate the tool.

[TonyG-UK]

Loving it already.

[dmcconachie]

Absolutely love this addon, Tim! Great work!