Waze Traffic Reports vs Speed Limits?

Hi,
I had an odd Traffic report pop up on my commute in to Nottingham this morning. A Waze generated traffic report appeared on the A60 southbound to indicate that there was a traffic jam and the average speed was 45 mph.
The section of road at the time has a speed limit of 40 mph but as the Waze editor/system doesn’t allow us to mark speed limits on roads (at the moment?) then this combination of features appears to be generating additional ‘noise’ on the Traffic reports than is necessary.

Is the assumption that there’s a traffic jam taken from the assumption that Primary Roads have a speed limit of 60mph or is it balanced against the average speed that Wazers are travelling through that section (makes me wonder if they’re consistently speeding? :slight_smile: )

Has anyone got any insight what makes this happen and if there’s anything in terms of editing that can improve the situation?
When I pause at traffic lights and the Waze client starts presenting me with useful updates from the community I’d rather not have 15 more Waze generated ones that might be unnecessary.

Cheers,
Jonathan

It’s calculated by factoring the average speed of the road segments, which Waze calculates from the GPS tracks of Wazers driving along. However, sometimes these get screwed up and have silly values.

Post a Permalink to the road segment in question.

Hi,

Happens regularly on the A611 from moor bridge to the City hospital as well. Here.

It is odd when it appears…

Des. . . :wink: