iainhouse wrote:You have my sympathies.
Nobody else seems have an opinion, so the best I can do is reassure you that what you have done looks perfectly correct. Without editing rights I can't check things like reverse connections, but I cannot see a single problem there.
The only real help I can be is to tell you you're not crazy - something screwy is definitely going on here!
Replacing R. da Encosta with a straight segment sounds like a reasonable workaround. It would be better that the client gives correct instructions with an incorrect visual, rather than the other way around. However, before you do this, have you tried sending a message to Waze Support - see if they can see any reason for this?
I've sent to support and I have to re-read the whole thread from the new WME editor as some waze admin told me they would look at it after the infrastructure and the wme infrastructure migration, so in the meantime I've checked and double checked and then redone everything in an attempt to solve it myself. As I see other similar cases, I hoped that others had gotten bitten by this possible rounding error. Unfortunately there's not that many cases that people drive everyday with so many perpendicular segments nearby so many nodes that people would notice it. I do because it affect my every working day
PS: no reverse or u-turn or soft or anything reported by the highlights. As I said, created from scratch, one by one, locked, q-w'ed all nodes, city and street names aligned, everything correct as far as I know.