Olestas wrote:I use departure, so I don't have to select several segments.

Where is the source of changes to algorithms?

Waze is the source on this. After our NA meetup in NY

shawndoc wrote:I checked with another local editor, and he's saying it works fine for him in production, but he can't get it to work in beta.

Oh well, since it looks like this is local to me, I'll have to assume its something on my machines that is causing the problem. Maybe a malware blocker or something.

Since you asked me about this, I've now verified that I get the same behavior from script version 1.5.6 installed in up-to-date versions of Chrome running on Windows XP and 7, and on Mac OS X 10.7, 10.8, and 10.9. All my machines can see the junction angles in the production editor, but not in the beta. Methinks it's as Alan suggested, a matter of the allowed URLs in the current version of the script. I guess we have to wait. At least the production editor has conversations and time-restrictions now.

bz2012 wrote:Hmmm. I do NOT see a 'Junction Angles' layer at all. The extension is in my extension list and checked to allow (had to override the "not from chrome web store" to do that but it is done).

This script has been available from the Chrome Store for quite a while now. Are you still using a really old version?

PesachZ wrote:Feature request...

The nature of this request stems from the sheer complexity of the routing algorithm decision on turn instructions to be given (or not) during navigation...

The suggested modification is to change the background color of the Turn angle bubble (currently green) when two adjacent segments are selected...

I think that any one of the options proposed would be a tremendously helpful addition to JAI. I enthusiastically support this idea!

One thing occurred to me as I was considering the color suggestions: We have some editors in our community who are colorblind. I believe that blue and orange are the most easily distinguishable colors for most kinds of colorblindness, and because turn angles don't have the same associations as red and green do with go and stop, we could avoid those troublesome hues in this context.

It doesn't work (at least on Chrome) when permalink contains segments

bz2012 wrote:FYI, if anyone is interested, I wrote an AutoHotKey scripted program that is essentially a questionair following the flow chart.
I include in this zip file the 'source code' and a compiled version so that you can view/modify/fix any mistakes I made. You can also just run the compiled version without needing to have AutoHotKey installed on your computer.
https://filestogeaux.lsu.edu/public/dow ... 6910YyqYmH
I release my code into the public domain.
Use as you like.
If you manage to sell copies, cut me in on the take.

It, essentially asks you the questions, as shown on the flow chart in https://wiki.waze.com/wiki/index.php/Ho ... _maneuvers, and tells you the final result.
EDIT: fixed wrong link to the wiki.

Further EDIT: I see what looks like an excellent page at
https://wiki.waze.com/wiki/Interactive_ ... _algorithm

I didn't have a chance to look at your script, but be advised that the algorithm just changed. It's documented in [NEW] Best Continuation algorithm has been changed

Sent using Tapatalk for Android 4.4.2

Hopefully there'll be a fix soon, I use this script everytime I edit. It was instrumental in deciphering the Waze routing algorithm too. I can't wait for an update, please.

Sent using Tapatalk for Android 4.4.2

milkboy wrote:

brandonrossl wrote:Does anyone have the ability to update the official Chrome add-on?

Update being processed. I just did some quick tests and the update seemed to work. Report any problems once 1.5.10 is available in the chrome store =)

EDIT: May take up to 60 minutes still...
EDIT2: Seems to be available now

Thank you so much for the quick update.

Feature request, I know it's been mentioned earlier but I don't recall seeing a response. I'm not sure how much effort would be involved so I'll make 4 suggestions in ascending order of complexity. If you could implement any of these upgrades in sure many editors would thank you, the first is probably easiest, the last most complex, albeit most useful.

The nature of this request stems from the sheer complexity of the routing algorithm decision on turn instructions to be given (or not) during navigation. Many editors do not understand the full algorithm, and seldom few have it memorized. I have done a lot of testing and work to simplify it as best I could in the wiki (with your help as you know - thank you [emoji2] [emoji106] ), but a tool in the editor that could indicate at a glance what to expect would ease a lot of confusion, especially for new editors. It would have the added bonus of allowing otherwise unaware editors to the fact that doesn't turn angles could produce different results, so these editors would be intrigued to investigate further, and learn about this concept.

The suggested modification is to change the background color of the Turn angle bubble (currently green) when two adjacent segments are selected.

Option #1
Use three colors, one for anything less than 44° (possible stay/exit instruction), one for over 46° (turn instruction), and a third for 45° (gray area to be avoided).

• <=44° should be a light-pale color (maybe blue or green), since this angle will not always give an instruction depending on the Best Continuation.
• 45° should be a gray, since this angle represents the gray area to be avoided, as based on averaging it could fall into either category.
• >=46° should be a standard color, perhaps the green you are using now, as this angle will (almost) always produce a turn instruction.

Option #2
The same as option 1 for 45°, and >=46°.
If the angle is less than our equal to 44° parse whether or not an instruction will be given based on the BC algorithm, and display a color accordingly. Use the algorithm flowchart in the wiki.
(If you choose to use this option, I'm working on an updated flowchart to represent the new algorithm changes)

• <=44° which will get an instruction should be the light-pale color (maybe blue or green)
• <=44° which will NOT get an instruction should be a white background

Option #3
The same as option two, but also considering whether the instruction will be "Stay" or "Exit" when less than or equal to 44°. This is based on the segment road type of both segments, and described in the algorithm wiki.

• <=44° which will get an Exit instruction should be light-pale green color, compared to a BGS (navigational signs for exits are green)
• <=44° which will get a Stay instruction should be light-pale blue color with enough contrast to differentiate from the pale green

Option #4
The same as option three, but also displays whether the instruction will be left or right.
Add a small "L" or "R", next or under the angle. Or to be globally useful add a "←" or "→" instead under the angle.

• Turns less than <=44° would be right unless there is a segment with a turn angle further left of this segment, but still below 45°.
• Turns above 45° would be based on their turn angle direction alone.
  
  Any option above would be useful and appreciated.
  
  Thank you. Please reply of you are interested in working on this, or not. Otherwise I can request it in the general forum to see if anyone else would be willing to take a stab at it. But being that your script already evaluates all the angles, I thought it would be the best fit.
  
  Sent using Tapatalk for Android 4.4.2

milkboy wrote:I had a look at the flow chart (which is really nice, as it almost condenses the logic into code), so now the feature should be easy to implement I gave it a go a while back, but realized that the guesswork for routing instructions back then was only half correct. Anyway, please keep us posted on any updates to the flowchart. I might have a look at implementing something tomorrow [emoji16] but no promises yet.

Excellent, thank you so much. All the changes to the flow are indicated in the message box on that page, and have to do with alternate names. I just haven't condensed the logic for them yet.

Sent using Tapatalk for Android 4.4.2

milkboy wrote:I had a look at the flow chart (which is really nice, as it almost condenses the logic into code), so now the feature should be easy to implement I gave it a go a while back, but realized that the guesswork for routing instructions back then was only half correct. Anyway, please keep us posted on any updates to the flowchart. I might have a look at implementing something tomorrow [emoji16] but no promises yet.

Have you had a chance, and/or any success with this? I completed a first draft of the new algorithm.

Sent using Tapatalk for Android 4.4.2