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