But I have triggered them 20-40 cars back while I'm still 20-40 cars back. That is waze doesn't yet know what my speed for the segment is. This doesn't usually happen when I am stopped nearer to the intersection.gettingthere wrote:I think this is due to segment speed. Longer to transverse the segment than the average at that time of day.jondrush wrote:I've observed just that. I've never triggered a traffic alert sitting within a few cars of a red light, but if I'm 20-40 cars back I have triggered them. Waze is a little bit smarter than the average bear . . .
Right, but it depends where on the road I am, whether or not an automatic traffic update is generated.gettingthere wrote:You are always on a segment if you are driving on a mapped road do data is being gathered which is being analyzed and feeding the system that determines whether to report a jam and to calculate and update the jam speed on the display.CBenson wrote: But I have triggered them 20-40 cars back while I'm still 20-40 cars back. That is waze doesn't yet know what my speed for the segment is. This doesn't usually happen when I am stopped nearer to the intersection.
This makes no sense to me. Intersections/junctions define segments. If you remove an intersection, you now have only one "lowest 50 meters" section when there was previously two. This is very likely to have an effect on the traffic jam algorithm.gettingthere wrote:There has been nothing stated in the posts from The Fej stating that the 'lowest 50 meters' is in any way tied to or related to an intersection/junction.
So removing the intersection on the Waze map should have no effect on the traffic jam algorithm. This is the point that a few of us posting in this thread are trying to make.
Did this fix ever get uploaded to papyrus?krankyd wrote: Note - Nov. 7th - the fix is not uploaded yet to the Papyrus. On the cartouche, it is already working as described above.
We will update you once uploaded and operational - should be in the next couple of days.
This needs fixing as a high priority, just about every journey I do I get directed though restricted turns, usually as I deviate from the route that Waze wants me to go (as it's down a Toll road) and it tries to make me do impossible or illegal U Turns.Shorty-CM wrote:There's definitely something wrong with the routing server regarding turn restrictions. I've been having a back-and-forth via email with them for some time about it, but I don't know if that's going anywhere.
I think this is the way it did work and the change has meant this is now not the case!Shorty-CM wrote:Hmm, so basically, this means if you ever touch any junction at all the only way to make sure the map data is correct is to then edit every single junction that exists in the entire map. Since touching one means you then have to touch the one at the other end of every segment attached to that junction you just touched. Ad infinitum.
Re: Modifying the lock option (and some explanations)