Show streets speeds all the time

[gettingthere]

its a bug then? I often go thru jams and waze does not update further road segments. It only changes to red the segment which i reported.

It depends on a lot of factors - some of which we don't understand fully since we are users of the system, not the developers. If the traffic jam is moving at 40mph and the average speed of that segment at that time of day is 40mph, Waze may not show it as a jam - even though the posted speed limit may be 65 mph. So to you, it's a traffic jam. But to Waze, it's not a jam since the traffic speed is the same as the time of day average.

Waze is analyzing the traffic of each segment as mapped. If you report traffic, Waze has stated that it gives double weight to a jam being created on that segment. But as you say, the double weighting seems to only be relevant to the segment where you placed the report. So if you commonly run into situations where adjacent segments don't update with the jam (may not update until several minutes later), try doing a manual report on each segment. Of course you should not have to place any manual reports since Waze should be doing all of this automatically...

[gettingthere]

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.

I can confirm that Waze ETA is affected by areas that are frequently jammed with traffic - whether or not there is a jam on the display. I notice this when there is a holiday and I can beat the ETA to my work by several minutes. Generally I can rarely beat the initial ETA on my daily commute.

Of course Waze has no concept of the speed limit - only the average speeds. But I understand what you are saying - if the average speed of a segment is 30 MPH at 8am and 65 MPH at noon that the slower average speed is due to traffic.

So in order for Waze to show a jam on a segment that has an average speed of 30 MPH at 8am, when the traffic is flowing at 30 MPH on a particular day they likely will have to modify their jam algorithm to also compare against average speeds at other times of the day. Likely this would really complicate their jam algorithm (and probably going to introduce other bugs...).

[MarcL20]

Hi, I made a quick search on the forum and didnt find it.
A nice feature would be having the streets speeds all the time on the client map. I dont know if this is a bug, but when I report a traffic jam, only sometimes the speeds appear, and the worst: the traffic jam seems to be reported just for that little road segment between the 2 knots. Some traffic jams are very long and that mislead any traffic jam information while doing routes. We also cannot see when the traffic jam stops.

If waze could grab every user speed even without the traffic jam and plot on the map, would help us a lot by knowing that the speed average there is good.

We also could have some troubles if it works like that. For example, if someone stops on a store without parking lot, waze could think that he has slow speed and plot wrong speed info on clients. Waze could then popup a message asking if he is in a traffic jam (i think it already does that, but just for reports).
Other way to solve it could be to just plot speeds on "Primary streets", "freeways" and "highways".
Waze could also have 2 modes: The actual one and this new one.
The segment speed could be changed only if other waze passes thru there to update road speed or after a time limit of 1h or 2h. (It could plot a greyed-red to show us that it was slow 2 hours ago, same for green).

Another problem could be the 2 way roads. how to plot both speeds? If both are good, plain green. Only one way, how its plotted nowadays. If one is fast other slow, I think half arrows could move each direction in respective color. I dont know if this could make you feel dizzy. But these are only few ideas.
=====================================================================================
Ideas aside:
The thing is, waze could still work as it does now, but it should show us better where the traffic jams goes to. Not just on that segment.

Sorry if something is not good explained. I didnt read it again before sending.

[MarcL20]

its a bug then? I often go thru jams and waze does not update further road segments. It only changes to red the segment which i reported.

[MarcL20]

Maybe its really associated to the speed waze has set in cartouche. Is there a way to set those speeds to actual road speed limits? Maybe waze is not showing slow roads because the real road speed is low and since its low and the traffic is slow, to waze, there is no jam.

[MarcL20]

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.

[MarcL20]

They could implement something to use both data: Max and average. Its not hard to do.

[MarcL20]

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.

[MarcL20]

Well, I just hope they fix this problem: The jam is long and waze only change the road to red usually only when I report a jam. Wazers go thru the roads that speed limit is 70km/h and waze has it with 30km/h in average. When in a jam, wazers go thru 30km/h and waze thinks its without jam.
I hope it wont work that way, or if so that they fix it.

Waze often makes routes with strange cuts via small service roads. This may also happen because of this. The primary road has the speed average lower than of the service road and waze sometimes makes crazy routes.

[MarcL20]

You may not like it, but it works. Waze knows that road is 30km/h, and it's calculating as such.

Any of the proposed suggestions will not help solve this problem. The only other way (in my mind) is to have hourly averages compared to the global average (displayed in Livemap / Cartouche). This would be the only way to have something similar to WYSIWYG. But it would still require implementation. Luckily, though, the (already existing) data would update itself and be somewhat correct.

Waze makes cuts because it's probably quicker at that time of day. If the main road is clogged, obviously the side roads would be quicker if there not.

Well, I disagree.
How can it works since the average of the road is 30Km/h while the normal road speed during times other than rush hours is 70Km/h? As I said, waze sometimes does stupid routes when its not necessary. Today, at late night, it made me go thru a desert road that had "speed reductors" and a longer path, just because it had a speed average higher than a shorter primary road. And I still say: Waze misses coloring red road jams just because of this average.