This is now happening in Production.
When you select a roundabout, uncheck the âEnable Roundabout Anglesâ option at the top of the box. That will get rid of the lines until fixed.
I have a fix for RA Utils that fixes the blue lines and makes the RA window draggable again. I have submitted a pull request but dont know when that might get approved.
You can load my fixed version with the TamperMonkey Import for URL utility and this link:
https://raw.githubusercontent.com/dalverson/WME-RA-Util/master/RAUtil.js
Hi, the Open Other Maps script was accidentally uploaded overtop this script as the newest update of RA Util
I donât know if this is WAD or Bug. The sum of the angles is 90.01 degrees. Shouldnât the sum be 360 degrees?
I think it is showing the difference from a 90 degree angle.
Yep, spot on 
It is the deviation that determines whether normal (left, right) or non-normal (1st, 2nd exit) instructions are given.
So friends, I swore I understood the logic of Wazeopedia USA. But see this case below, if the angle showing is the difference to 90 degrees. In this roundabout below, it should be considered non-normal (take first exit, take second exitâŠ) but it is being considered normalâŠ
I didnât understand the logic. Can anyone explain why?
Well, trying to understand my previous post, I did some tests and came to the conclusion that the information from Wazeopedia USA is not 100% correct. There is some rule that also considers the angles of the segments connected to the roundabout and not just their internal angles. See my test below:
Now the question remains. Whatâs the logic? We need to understand exactly how Waze defines a roundabout as Normal or Non Normal so that we can edit the map with quality and avoid wrong directions.
Hey.
This is an excellent point, but this is why we have JuBRA and now paths.
We should not rely solely on heuristics, especially since it smells like you might wanna change the angles (that should reflect reality) in order to meet these heuristics.
The correct way to do this here would be put JuBRA or paths and set manual overrides to ensure the behaviour you wish to have while accurately mapping reality.
This PL screams for JuBRA TBH!
Did a quick mapping to show what I mean (donât worry, I didnât save⊠:D)
1 Like
Obrigado pela resposta. Alguém pode mover as postagens mais recentes deste tópico para outro tópico? Desde que entramos em um assunto diferente do script RA Util.
Eu te mandei uma mensagem privada. Resumidamente. Acredito que devemos usar o JuBRA (que sĂł estĂĄ disponĂvel para editores de nĂvel 5+.) em casos especĂficos onde nĂŁo Ă© possĂvel resolver com ediçÔes normais. Para isso, precisamos entender a heurĂstica (a lĂłgica de programação) que foi utilizada para definir uma rotatĂłria como normal ou nĂŁo normal. Desta forma, editaremos com qualidade e nĂŁo serĂĄ necessĂĄrio deixar o usuĂĄrio frustrado. Sem entender as heurĂsticas, temos esses problemas em vĂĄrias rotatĂłrias, principalmente depois que começamos a desenhar as âperninhasâ para fazer a rotatĂłria se adequar Ă realidade. SĂł o identificamos depois que um usuĂĄrio frustrado abre um relatĂłrio de bug.
I believe this Wazeopedia text should be updated, with the help of Waze developers, who created the rule in the algorithm that defined the roundabout as normal or non normal.
The JBs and Paths are great but it would still be nice to know what angles trigger normal vs non-normal instructions at roundabouts. Equipped with this knowledge we will better know when to use the tools you mentioned. The script this post is about helps us with the instructions. @Rickendude Can you please share how the the instructions are calculated in the server/ client side. It seems like there is some kind of magic sauce that includes departure angle of the segment going out from the RA segment, the amount, of segments between the RA-in and RA-out segments, the angle of departure from the RA-in to the RA-out segments. You can see in the CC thread that there has been misunderstanding about the instructions for a while.
The problem with not knowing what instructions are given without using JBRA is that when we map things we may not know if the JB is needed, which will cause problems down the line with poor instructions given to the Wazer.
Thanks.
Thanks guys.
A few things regarding your comments:
- I totally agree that we should reflect the heuristics in WME, this is planned as part of the routing simulator, so for example: Youâd be able to check how the instructions will look like in relation to a recent edit, that will include LG (with far lanes) and also TI.
- (And I cannot emphasize this enough) - Edit the roundabouts with the right angles, in a perfect world youâd have the heuristics reflected but under no circimstances should you bend a segment to hit a specific heuristic! you should map reality and then if the heuristic doesnât catch it - override manually
- Specifically for Brazil I remember that during the Mega Meetup one of the coordinators agreed to reduce the paths requirement to L4, please reach out to the coordinators as at least from my perspective this is totally fine if they are good with it.
- Iâll ask Yigal about the current heuristics, but I am not 100% sure it would be a straighforward answer which is why I think it would be simpler to simply force the instructions using paths.
HTH.
thank you for Answer!!
Sorry, I didnât understand exactly. Is there a project so that the roundabout instructions are visible during its editing (creation?)
We need to know this. Even if this function is released for a lower level, not everyone will be able to understand its operation or correct it without the help of another editor, the same problem occurs for anyone creating a roundabout. New editors will create roundabouts and problems will continue to occur. It will be much easier for waze to explain to us so that we can update the manual, or create a native function in WME that shows us the instructions that will be reflected in the application. I believe that Waze takes user ratings and comments very seriously. In Brazil, for example, Waze had an overall score of 4.6 for a long time. Currently the app grade is 4.3.
I took 5 minutes of my time and ran through the last 100 reviews on the Play Store and the average was 3.08. About 2 months ago I had done this too and the average was 2.98. This indicates that there is a downward trend, there are a lot of negative reviews. We need proactivity. Waiting for the user to complain is not a good solution.
Hello.
The script is not working anymore, neither in production WME or Beta. Any news about it?
Thanks in advance 
What version are you using? It seems to be working fine for me.
Version 2022.08.12.03, I think itÂŽs the last one. It was working two days ago.
Does it not load at all? I just adjusted this RA.(unavailable attachment: ra utility.png)
Not at all, it doesnât even appear in the left pane.
It is working for at least two of us.
I would suggest reinstalling the script first. See if that fixes it. If it doesnât, try running the script as the only one. There may be a conflict with another script or extension.