[I posted this separate of the 3.6 feedback thread because I am unclear if it is a client or back-end routing issue.]
At the meetup last weekend bgodette and I noticed as we drove through this intersection
it failed to provide a right turn instruction into the cloverleaf. This is a pretty common bowtie layout for these interchanges to prevent through traffic from getting off and on the freeway. These interchanges are common in California and I have been ensuring most of them have this bowtie restricted straight through route set up. They have been working fine for months.
We were not sure why the problem happened here, so we came up with the hidden stub turn from that junction that provides a choice forcing the routing engine or client to announce which of the active turns to make.
Today when I drove through this intersection
, for the first time since I created this junction many months ago, I did not get the right turn instruction. I have gotten it every time I have gone through here until today.
Something has changed in either the routing engine or latest client. I am pretty sure this is the first time I have driven through here with the latest client. I am not sure if the editor has received any minor updates (prior to the beta release version going live). My assumption is this came from the latest client release or is a change in the routing engine (for which we have no visibility). I think this change breaks functionality in the client that used to work as desired and we should push it as a bug back to Waze rather than changing all the bowtie freeway intersections like bgodette and I did in Sunnyvale above.