Looking to get the lock level lowered to a 3, the Waze SL is incorrect on this street. Was there today and took note of the change points and locations.
unlocked
All done, thank you.
If you divide a segment, the initial segments list does not work for relock.
I know I am an grown boy and can do it myself.
I leave it as is just to show you
Please redo the segments list to relock.
By the same time review the turn restriction here
And direction on that segmentwho should be one-way
I don’t point anybody here, it was surely that way before
It is simply an observation please adjust it
Wow, I hadn’t even noticed that that one segment was showing as two-way, thanks for pointing that out. I’ve corrected it, thanks for the help.
But that Fairway Rd N should really be shown as two one-way streets. They are far enough apart with a physical barrier. Is that something I am allowed to do? Or should I leave it for someone “more qualified”?
Have you read this
When to divide a two-way road (and when not to)
To me, there is no need to divide it
I will ask a champ opinion on that.
Yes, I had read the guidelines before, but not lately. Thank you for providing the link. I read them again, and two conditions (only one is necessary to qualify) are met that allow for showing it as two one-way streets:
U-turns are required to properly make turns from public drivable road types that are blocked by a median. Motorists coming out of Eden Oak Tr cannot make a left turn because of the median. They must turn right and go around the roundabout.
GPS tracks show a clearly definable and continuous gap (blank area) between the color-by-azimuth arrows at the 100m/500ft zoom level
This street does qualify. I’ve seen residential streets in Kitchener Waterloo that the two one-way segments are much closer together and someone has showed them as divided.
I know the guidelines say’s
A road may be divided when any …
But on top of that the first rule into Waze is to keep it simple.
Let say if it was already divided i won’t undivided because of that rule
Well, that’s just my thought.
Here there is no good or wrong answer
but only a décision wich i’am not able to take
I ask MushyMedic to look at it.
Let’s wait for is answer.
Alright, we’ll wait for his answer. But just in getting back to your opinion on the matter, you don’t think it needs to be shown as divided, yet two of the guidelines are clearly met. Just curious as to your reasons for leaving it as is. Don’t get me wrong, I’m not judging you, I’m still learning (as we all are), curious as to your thought process. Again, motorists coming out of Eden Oak Tr cannot make a left turn because of the median. In the mean time, we’ll wait for his response.
Hey guys (sorry if I interpreted in error),
Thank you for reaching out to me. This is exactly what the community should do and I really want to work in the future to grow this community.
So when to divide… in short, when only absolutely, unequivocally, necessary. And why???
A local editor and I in Winnipeg have been running some tests on roads exactly like this. How to improve them, how can we reduce the routing error, eta errors, and such. Also with u-turn prevention being disabled, and now requiring junction boxes to prevent L-L turns, divided roads are really ineffective. They create routing errors and upset users, and if a user gets upset, they generally erase the application. We need to consider these issues heavily before adding divided roads.
So how does Waze look at divided roads:
Looking at divided roads, our minds are able to think of them as the same road, one heading one direction, and the other in the opposite. To the Waze routing engine, it looks at them as two unrelated completely different roads with different directionality but for some reason, the same name. Oh and they eventually meet too (usually). Which causes some unexplained behavior.
As an example which I believe you two already understand, but just in case, to the Waze routing engine there is not difference between these two example:
Two different roads that are one way.
and
A divided road segment.
So, does this really cause the routing engine to mess up? You be the judge:
In this example, I moved the “A” start node just a little, and look at the differences the divided road cases:
After the PLR
Just before the PLR
Between the intersection and PLR (No idea, but the routing engine dies)
So in the case that you provided… is there a way that correct routing can be accomplished without dividing? Yes there is, and you have accomplished this with a simple turn restriction. One of the things I still struggle with is making the Waze map look like what is in front of the user while they drive. We are not the normal user. We look at the app while we use it, we study it, look for issues, etc. The normal user sets their destination and listens. Waze has tested this, and we are not the normal Waze user. So we need to adjust our thinking some times. Waze isn’t about looking pretty, it is about simple, accurate, and efficient routing of traffic on a road system that resembles the actual roads but doesn’t necessarily mimic them.
I completely get what you are saying about not being able to turn left, and shouldn’t we visually provide the correct routing and visual representation. And the answer is, only if having an undivided road does not allow us to accurately route the user.
MushyMedic
Thank you for that very well illustrated answer. I guess we’ll leave it the way it is. Are we going to see you in Montreal in a couple of weeks?