kuduboet wrote: I tested it with my Garmin today and the Garmin clearly stayed in the local lanes and when I was being navigated, Waze "drifted" into the express lanes but when I was later driving with Waze, but not navigating, it showed me staying in the local lanes. So to me it confirms it is some sort of logic issue with Waze when navigating, not an accuracy issue.
Sorry, I meant another GPS app on the same device that is running Waze. I have no doubt that GPS is accurate enough to make a distinction (when using a good receiver, with good ephemeral data, a good antenna, good antenna orientation, and good satellite visibility). But a GPS receiver in a phone with obscured satellite visibility and who-knows-how-much latency in calculations vs. rendering (plus whatever other tradeoffs the manufacturer made in order to cram that much functionality into what is primarily a communication device)-- maybe not (or maybe not, given the variability of RF equipment, on a specific unit at a specific point in time/space
Note that the satellites are always moving, so to even begin to compare receivers you'd need to be at the same place at the same time and in the same vehicle with the antennas in the same place/orientation, etc. That's why running another app on the same device at (roughly) the same time would help pinpoint the source of error(s) in this situation.