https://www.waze.com/editor/?env=row&lon=0.06297&lat=51.48856&s=121633239&zoom=8&mapUpdateRequest=10470402
According to the wiki, these are two parallel segments with a segment under 15 metres in between, so this should not have happened.
Is there any clever way of avoiding this, or take it as a one-off incident?
Note: I cannot edit this as it’s locked to Level 4 anyway, so if someone can take a look for me that’d be brilliant!
Hi,
I’ve added a junction box and disallowed the u-turn route.
Just as an alternate idea if you come across roads at your level, you can better control u-turns by using a bow tie junction, though this can upset some wazers as it looks odd.
Nice one Stu, thanks mate!
Indeed Chris, but I couldn’t even throw a junction box on this as it was over level 3 :lol:
There have been reports (e.g. this one) from other parts of the Wazeosphere that the u-turn prevention mechanism wasn’t working properly.
This does raise the question over whether we really should still be relying on constructing junctions in very specific ways to prevent u-turns and other unwanted directions being given, when the only thing preventing these instructions from actually being given is little more than a hack of the routing algorithm which can, and as recent events have shown, does stop working from time to time.
The bowtie solution, whilst suffering from the problem of not being an accurate visual representation of the junction (which, depending on the size of the junction, may then cause some confusion when the junction is rendered in the app), does at least rely on the fundamental routing rules rather than specific hacks, so if the server fails to handle the bowtie correctly then we’re in serious trouble…
Junction boxes ought to be the solution, given that they provide a rather elegant way to define exactly which paths are and aren’t allowed without the need to go clicking on segments and seeing which arrows light up green and red, and without the need to collapse the entire junction down into a single super-node through which every route must pass. Buuuuut, until such time as they’re made available to lesser mortals, or at least where we’re allowed to make non-destructive alterations to the segments within a JB which don’t affect the operation of the JB itself, they really aren’t a solution at all - if every junction where a JB could be of use actually did have a JB applied to it, the editor request forum would probably go into meltdown with all the requests being posted requiring a L5+ response…