Let me put it this way – something definitely changed rather recently with the interaction between restrictions and destination road selection. It used to be that Waze would force itself through a restriction if it knew your destination to be on a particular segment. Now, Waze will choose another nearby segment.bgodette wrote:I'm not sure anything changed since the introduction of TBR. Remember they initially said "works like Private" which we took to mean that there were routing penalties associated with use, then there was some mentions of it working like disconnects. Later we got direct confirmation from an unfiltered source that TBRs worked like a disconnection, as if the segment or turn didn't exist. This later information agrees with the above behavior IF the "works like disconnection" for TBSR is evaluated for exiting the segment. There's an old discussion about PLR/Private penalties for why the evaluation is on exit, and code reuse/re-purposing leads to TBSR getting the same evaluation point.
Basically there's an edge case where terminal route behavior isn't correct, and acknowledge as not being correct, for TBSR cases when the destination is on the restricted segment, but works as designed if the destination is beyond the restricted segment.
Restrictions are the same, it's what destination-road matching does with restrictions that's changed (or, really, that it does something at all).
-
sketch
- Waze Global Champs
- Posts: 6770
- Has thanked: 1118 times
- Been thanked: 1664 times
Re: Jolly editors