The route exiting from 404N to 1900 Sheppard Avenue (just east of the exit) is very slow in Waze at certain times of the day. Checking with Route Speed, it is typically slow during rush hours but is extremely slow in Waze at some times in the late evening and overnight. This is almost certainly an error and there is a UR here complaining as such. Because of this, the obvious left turn to exit is sometimes replaced with a right turn heading to Don Mills and circling back.
We had a problem like this before at Major Mackenzie and Leslie in Richmond Hill which didn’t resolve itself over time. Since Waze only stores 3 weeks of speed data, would it be more expedient now to just recreate the segments to relieve the problem instead of waiting?
I think this exit can be very slow but the correct slow speed data is somehow being extrapolated to other times.
Sorry, I don’t have an answer to the question you asked about fixing it.
I agree that it is most likely an error in the data.
However, you should also consider that someone could be out walking their dog, jogging, etc. with Waze running. Unfortunately, it happens – it’s the nature of a crowd-sourced system. If the traffic pattern was low enough that late at night, the data could be significantly skewed by just one user with a habitual slow “drive”.
Unless you can somehow get Waze staff to identify and block the specific user drives, there is no fix for this scenario (other than get more Wazers out there to dilute the ‘speed pollution’).
I just want to avoid the months it took to try to resolve the issue. It would be great if Waze could investigate but even if we’re not 100% sure of the cause, the impact of losing speed data for this one segment would be small.
I will take a look in the next couple of days and see if we have an issue here that require intervention or not.
I can tell you that in some cases I was routed through the collector, coming from HWY 401 W to NB Hwy 404.
Recreating the segment is last resort measure.
Sorry for not getting back to you sooner.
I looked at it and it is seem to be showing some slow speed in unusual times of the day.
Before I ask support to look at this, can you tell me if you had noticed that by driving the segment or a UR made by a user?
Looking at the nearby UR the editor confirms that it may take 3 cycles to turn left, which completely explain low single digit speed average for the segment.
What seem abnormal to me is that there are slow, single digit, speed for the segment in the middle of the night, when there is no traffic.
It is possible that Waze way of smoothing existing speed average records over time that has minimal or no data went wrong.
I will report this to Support and see what they have to say.
Please be patient as this may take time.
I suggest you leave a note on the UR asking editors to leave this open.
I think you are right about the smoothing. When it’s busy, I believe this left can be very slow since it is a three phase signal. The smoothing of abundant slow rush hour times seems to override smaller amounts of data points at other times.
I was just playing with route speed and found some weird behaviour. I set up a route from the highway to just left of the exit. I then set the date to Tuesday and time to 14:30. If cursor the time repeatedly back and forth over 14:30, I am usually directed to turn left but once in a while I’m told to turn right and make the big loop that the reporter experienced.
– it’s the nature of a crowd-sourced system. If the traffic pattern was low enough that late at night, the data could be significantly skewed by just one user with a habitual slow “drive”.
