Sometimes we have a "turn left" or "turn right" instruction, when there is no other way to go...
Example :https://world.waze.com/editor/?lon=1.33 ... s=62075349
GPS says 'turn left' when you go to point A to B. No instruction will be better.
This example does not happened before 3.5.
This should be discussed somewhere else, but I've seen similar stuff happening some days after the last international mapdate so this kind of instructions may be corrected by editing the map, but others may be a change on the backends.
To keep on-topic, it would be nice to have a feature on the editor where we could select two points and it would tell us the instructions between those points, according to the new map design, so we could preview the edited map and fix it until getting the right instruction instead of waiting months until getting it correct - sometimes it's hard to make the right angle to get nothing, keep or turn instructions. It would be enough to support a single instruction, but it would also need to support picking one segment before and after a roundabout to see the "take the nth" or "turn left/right".
For your case I'd just decrease the angle to less than 45º and the message would go away. See screenshot.
ultragreg wrote:With some Y roads, there is also the problem, example before or after a roundabout. The logical is to go straight. A 150° turn is not possible... (and turn is already forbidden on the map)
I personally kill all those Y/triangles before and after a roundabout, they are worthless and just causes problem. Here in Portugal most roundabouts are just perpendicular crosses with a roundabout in the middle
so I've been redoing them all by deleting them, connecting the 4 segments in a cross, and redrawing the roundabout over it, locking the roundabout, qw'ing all nodes and after a mapdate, the roundabout will tell me "straight ahead/turn left/turn right" instead of "take the 1st/2nd/3rd exit".
I also try hard to keep single segments instead of two parallel segments when they are not needed, or else they tend to switch from unidirectional to bidirectional and then start telling me "keep right" when arriving at the split. The simpler the better, adjust the map for the instructions and the gps lines, never for satellite images.
Other example, but I have tried to edit the road to don't have the instruction (and waiting an update to see the results)https://world.waze.com/editor/?lon=1.34 ... 6,62080099
B to A : we have currently a 'turn right' instruction, which has no meaning in this case. The complete instruction is : stay left, then turn right.
On these ones I make the left exit a ramp, because with two primary streets there is a chance that going straight ahead will tell you "keep right". On the other hand, on these particular cases I'd rather just get the "keep left" and avoid the "turn left" at the end, because as soon as you enter the left lane, there is nowhere else to go. Here's an example
where it only tells me "keep left".
Now probably related to the extra instructions, I have some cases where everything was perfect when the mapdate happened, and then some days after that some additional instructions started on the client, and there was no mapdate, no new client, so it must have been something changed on the backends. And now I have no idea what else to edit to fix them!
For example, on this one livemap
, going north->south, I get a "keep right" that should not happen. Before the mapdate there was no node to keep the line straight, so indeed it was an expected instruction before the update, but I got it fixed and it was working for some days.
Another example is this one livemap
where it was also working, and now it tells me twice "turn left".