Navigation conundrum

[timl2k12]

I live on a two way north-south street. If my destination is south, waze always takes me north first to travel around the block for no apparent reason. There are no map errors that I can see. All the roads are 'back roads'. Nothing special about them. If it is helpful, the road is N Edison Ave in Tampa, FL between Perio St and Perdiz St.

[AndyPoms]

Waze assumes you are travelling in the direction you were last driving when you shut the app down.

If you drove home heading north, Waze will route you driving north the next time you start going (and vice versa). If you start driving south Waze should recalculate or you can do what I do, start driving in the correct direction, let Waze realize it, then start navigation.

If the above doesn't apply, please post a Permalink so we can look at the area.

[timl2k12]

OK, I'll try that thanks.

[RallyChris]

Helps to provide a permalink in the future. Luckily I was able to find it on first search, but without a permalink searching for a random street in a place you are not familiar makes it hard to be motivated

I would suspect the issue is with this segment

https://www.waze.com/editor/?lon=-82.46 ... s=70439083

Note how the node doesn't have an arrow at all for the cut across segment. I would disconnect the segment and try reattaching it. If it is connected correctly, then you should get an arrow to tell if the turn is restricted or not.

Otherwise, you might need to provide a permalink example of bad route from the livemap.

[timl2k12]

Very interesting, thanks. I hadn't noticed that. I don't think it relates to my problem as waze would not need to route me there but as the author of that section I'm glad you pointed out the disrepenecy. Thank you.

[timl2k12]

Perhaps it is in the faq or one of the wiki's, but I wasn't able to fix the "missing turn" unless the one way segment started at point 'A' and ended at point 'B'. The way it had been was it started at point 'B' and ended at point 'A'.