[Script] Livemap Navigation Browser Addon [Deprecated]

[deeggo]

And so does a continue straight instruction.

[Timbones]

Looking in the data from the routingRequest, I can see a bunch of new fields: tts, additionalInstruction and isToll. Not sure what they mean, and I've not seen them be anything but null or false.

Anyway, I've been working on the script today, and have this beta version for you to try:

• Treats NONE instructions like it does for CONTINUE (NA only)
• Adds images for each turn instruction (borrowed from editor)
• Shows links in popup for next and previous instructions
• Will show above fields in popup if they're become interesting

[AlanOfTheBerg]

Tim, I agree with your assessment. Earlier, I didn't pay close enough attention to where the junctions were.

Andy, the instruction used to be called "continue" in the route list, and now appears to be called "none" and has always existed in the instructions passed. However, the app doesn't receive an instruction for this. Waze knows we want to be able to have this for specific situations, but in general, no instruction is needed to stay going straight through a 4-way intersection. You may also be interested to know that the UR routes used to show this continue instruction as well. Note the graphics and information on http://www.waze.com/wiki/index.php/Upda ... ted_Routes

[Timbones]

It looks like it's only happening on the NA server, with 'none' appearing where it used to have 'continue' instructions (that weren't shown). I'll have a look at fixing this over the weekend...

[AndyPoms]

Doing a little research with the edit map and the "NONE" markers. What it looks like to me is every junction that has no effect on the directions gets a "NONE" marker. Do you agree with that assessment?

If that is what's actually happening, it would be nice to be able to get access to that property. So we could "force" a direction prompt (i.e. "Continue Straight on <RAMP NAME>" when a surface streets leads directly to ramps)

[HavanaDay]

I see the same today. A few directions, lots of "none" rows, and a few more directions.

EDIT: The "none" entries correspond to mileage markers every .1 miles. They've definitely made changes to the response of the RoutingRequest as these "NONE" markers have not existed until very recently. The returned JSON text is significantly longer now, and full of those NONE entries.

Doing a little research with the edit map and the "NONE" markers. What it looks like to me is every junction that has no effect on the directions gets a "NONE" marker. Do you agree with that assessment?

[AlanOfTheBerg]

I see the same today. A few directions, lots of "none" rows, and a few more directions.

EDIT: The "none" entries correspond to mileage markers every .1 miles. They've definitely made changes to the response of the RoutingRequest as these "NONE" markers have not existed until very recently. The returned JSON text is significantly longer now, and full of those NONE entries.

EDIT2: The returned code also now includes a "TTS" entry. It looks like Waze is preparing to enable their own navigation list, which should better mirror exactly what the app TTS would read out. There is also a value for "additionalInstruction" which I don't recall seeing before.

[HavanaDay]

Is this broken for anyone else today? Tried to do directions from Charlotte, NC to Upper Marlboro, MD and the direction list seems to be working just getting a lot of the text "none" listed for non existant turns.

Never seen that before.

[Caradellino]

Thanks for the info, Alan...

Somehow I had a feeling, the situation would be like this...

I already suspected, the tool would mount on the basic routing done by the livemap itself - still I had a vague hope, it would do the trick by itself.

...but still a man can dream

Once again, thanks anyway for your time - especially if there have been other threads already which I have been too lazy to look for ...

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