AlanOfTheBerg wrote:Speed limits are only a nice-to-have feature. Waze works with real traffic data, so regardless of what a segment's speed limit may be, Waze works off of what the limit really is at any given time of day. I also would seriously hate to see every single segment on the entire map colored mostly green, with sprinklings of red, orange and yellow. It would be a horrible mess and would be pointless. And actual speed relative to speed limit is a useless data point. What is useful and actionable data, however is actual speed relative to expected speed that time of day.
I'm not sure I agree with this. I can see the argument and it's not without validity but traffic is traffic, even if it's typical for that road at that time of day. If I don't normally travel a road and I see that it's green, I have no expectation that there is "traffic" on that road. Even if I travel the road every day, I would like to know how bad the traffic is.
I drive the same route, pretty much, every day to and from work. It's 50 miles each way. I have two main choices to get to and from work. One is Route 295 and the other is the NJ Turn Pike. 295 is a little shorter but they are both almost the same. the TP is a toll road, 295 is not. The traffic can really vary on the best route ( 295) quite significantly. I don't know what waze thinks is the normal speed at rush hour but if there is traffic I need to know what that means. Sometimes there are traffic "pins" all over the map but waze will report that the road is green. I guess it's because waze knows that there is normally traffic there so it ignores it? So that makes it harder for me to decide which route will be best. The other day I ignored the pins and trusted the red/green and stuck with 295... It took me 2 hours to go 50 miles. Worst commute I have ever had. Normal time is 1 hour. I assume it was because Waze knows there is normally traffic on that road so it didn't alert me?