MarcL20 wrote:Thats a problem then. We should be able to set the max speed of the road. With jams, people driving so slow and lot of data that corresponds to wrong road speed, that average will never go up.
bgodette wrote:MarcL20 wrote:Thats a problem then. We should be able to set the max speed of the road. With jams, people driving so slow and lot of data that corresponds to wrong road speed, that average will never go up.
It's not a problem. The averages are not for the entire day, but rather some smaller amount of time, however Waze hasn't said how small.
AlanOfTheBerg wrote:But the point still stands: just because traffic moves at 1/2 the speed limit for two-hours on specific segments during the evening doesn't mean, IMO, that Waze should consider that normal and not report a slowdown.
CBenson wrote:IMHO, it should consider that normal and should not report a slowdown. I find the Google traffic maps that have all highways here marked red during the rush to be most unhelpful. What's the point of alerting me to a fact I already know, that the traffic is slow when it always slow during the rush.
AlanOfTheBerg wrote:I'm not sure I agree, actually. But beyond that, if it considers that a road is running at its normal speed which is 1/2 the speed limit, is this affecting traffic avoidance? As I type this, I'm thinking "it shouldn't" and "I hope not" because traffic avoidance should still be based on transit times compared to alternate routes.
MarcL20 wrote:They could implement something to use both data: Max and average. Its not hard to do.
MarcL20 wrote:The hardest one we already have that its the average aquired by the client. Adding a Max speed in database is simple since it will be done by the editor and is just another data field that you will add to waze road registers. I dont know how is waze algorithm but instead of comparing just with the average, using existing methods "and" maxspeed shouldnt be difficult.
Users browsing this forum: No registered users