ETA & TBR during holyday
Some working week days might be a holiday once a year for some national celebration, and should be treated specially, not only for the ETA calculation, but also for TBR (Time Based Rules) for routing.
It might be an 8th day of the week with its own stats and be activated for requiring countries based on a given dates list .
On the weekdays that I’m working on the run up to Christmas waze is calculating a journey time much longer than I’m expecting and indeed much longer than it has taken me. Can the calculation be amended to take into account this pre holiday period and look at wazers on the road more than using “normal” traffic conditions?
הוויז לא מעריך נכון את זמני ההגעה בשעות הבוקר בערבי חג, הוא מראה זמן כמו באמצע שבוע רגיל.
גם בראש השנה וגם בערב חג סוכות - הזמן המוערך היה ארוך ב 30 דק' מזמן ההגעה בפועל.
Waze takes historical data into account when showing ETA's on the route calculation (and the alternatives route calculation).
It would be better that the historical data is based on e.g. 'a monday in August' than just on 'a monday'.
In e.g. holiday periods, the ETA takes historical data into account of days where there is much more traffic in none holiday periods.
This could result in much more ETA calculations during specific periods.
The system algorithms need to be adjusted to account for holiday travel periods. Yesterday I headed south from Bow, NH to Boston and beyond on Route 93 south. It was a Friday after Thanksgiving and Waze showed a total travel time to the destination that seemed very long and the app was vectoring me on a different route. Local traffic radio showed no traffic on my intended route. There were no incidents. Waze was clearly calculating times and assessing routes based on a "normal" Friday. It wasn't a normal Friday and we breezed in and through Boston and arrived at our destination in the 2 hours and 20 minutes I had anticipated.
I understand that Waze uses historical information plus telemetry from Waze users to forecast traffic conditions. This usually works, but fails dramatically when traffic is atypical such as on a holiday like Veteran's Day (which was two days ago) in the US. Waze initially predicted that my drive to work would take 1h12. It actually took 42 minutes, during which I received a few "traffic has cleared up ahead" messages and one "traffic has gotten worse message" with a predicted seven minute delay (which was quickly negated by a seven minute gain from "clearing").
I'm certain that there weren't any significant delays on my route. How can Waze be improved to handle atypical traffic days like this? Possible alternatives:
1 Add a feature allowing a day to be designated as "atypical," which would then result in less reliance on history?
2 Allow the day to be identified by name so that history for that same day in prior years can be used for predictive purposes?
3 Change Waze to identify atypical traffic days when traffic doesn't build as it typically does?
4 Reduce reliance on history?