The driver (en route to the MassPike) reports being instructed by Waze to detour off Route 9 - all well and good (could have been snow storm-related delays on the more direct route), but Waze routed through a parking lot road instead of using the off ramp to Route 27. Shoudn’t Waze have avoided the PLR?
It makes sense (except for the PLR) if Waze was redirecting the driver to route 27 north (N Main St), then to route 30 west - which brings you to the MassPike.
Curious to know what it was - I was just looking at the 9/27 intersection using WME Route Checker (and then Live Map), and routings starting on those segments (showing as edited by you today, but would not have updated yet) behave as though that segment is the eastbound direction. Weird. Adjacent segments are OK.
They look fine in the editor, but this might explain the weird routing originating in those segments (still present this morning, perhaps will update by tomorrow).
Response from a routing expert, regarding Waze routing through the PLR:
“Took a look finally at that UR in Natick. Definitely shows Waze routing the user through a PLR, but no suggested route before the PLR. This tells me that he missed the first turn Waze gave him, and the turn onto the PLR was following a recalculation. It is my pet theory that Waze can ignore most or all penalty based prohibitions within very close proximity to the beginning of a route.”
That one looks like he tried to get on Rt 9, and Waze directed him back to his original road. I wonder what was so bad ahead that Waze was directing people around it that fiercely.
Hmm. This is getting very interesting. In Live Map, today, Waze is definitely trying to avoid Route 9. (This was a route from a point on Route 9 westbound, between Weston Rd and Lexington Rd in Wellesley, to the MassPike entrance on Route 30 near Speen St. (The only problem reports are people reporting potholes.)