It's incessant for me; a significant part of one of my frequent routes is on the service-drive that parallels a major freeway, after taking an exit, but prior t

It's incessant for me; a significant part of one of my frequent routes is on the service-drive that parallels a major freeway, after taking an exit, but prior to diverging. Depending on traffic, though, it may also be advantageous to stay on the freeway, so both are valid parts of the route. If Waze instructs me to take the exit, then it assumes I'm on the service drive, even if GPS says I'm still on the freeway. And vice-versa, more problematically -- if I impulsively take the exit, it assumes I'm still on the freeway even if GPS clearly shows I'm on the service drive. (I can confirm this by running a spare laptop with a USB GPS as a logger, while my iPhone runs Waze. Overlay the GPX on a map later and it's super obvious whether I took the exit or not, but either the Apple location provider or Waze staunchly ignores reality in favor of obsessive road snapping.) Where this gets stupid is, if there's a traffic jam on the freeway and I dip onto the exit to avoid it, now Waze sees me flowing freely down the service drive, assumes that it's the freeway that's flowing freely, and disbelieves other users who report traffic there. Even as the service drive curves and diverges and I follow the curve, it doesn't retroactively say "Oh jeez, he must be on the service drive after all, adjust the previous data to apply to the service drive and not to the freeway!". So the bad data continues to corrupt the traffic picture and encourage other users to get stuck in traffic they can't report.