[seanp2k2]

Ageee when Google, who has been in the maps and software game much longer and with many billions more invested than any car company, can’t even tell that I’m on US101 on the HOV ramp and not on a surface street under the highway for that ramp where that Tesla driver using Autopilot fatally crashed into the barrier in Mountain View ( https://www.ntsb.gov/investigations/Pages/HWY18FH011.aspx ). When I drive there, Google Maps via CarPlay consistently tells me to make a U-turn, not knowing where I am, as if it doesn’t have access to accelerometers or speed data or vehicle heading information such that it could reasonably conclude instead that the GPS is a bit inaccurate and/or there are multiple ramps in an area and without reliable elevation data, the vehicle could be in a couple of different spots, so go with the most likely guess of “the vehicle did NOT jump over the barrier while traveling 65mph+ and end up on a surface street (supported by accelerometer and compass data) and is just on another ramp”. It blows my mind that they’ve had this bug for at least a decade. I actually keep a list of Google Maps bugs that they could fix and have been thinking of applying there specifically to go fix them, since somehow everyone else at Google seems unwilling or unable to address these for reasons that I can only assume are ~corporate complacency.