Rideshare and delivery platforms log an enormous amount of GPS data, far more than most passengers or attorneys realize. Every trip generates a stream of location points showing where a vehicle was, how fast it was moving, and whether it deviated from an expected route. In litigation involving driver conduct or passenger safety, that data can be objective evidence in the case. GPS records can reconstruct a straightforward timeline of a trip. Without the GPS records, timelines are filled with unanswered questions.

Analysis of GPS records helps rideshare litigation attorneys visualize timelines and determine how a trip unfolded. These records can reveal sudden detours, interruptions and deviations from the expected route, extended stops at unexpected locations, the proximity of the driver to the passenger before and after pickup and dropoff, and even if a driver attempted to go “off-grid” by closing the app or turning off his GPS receiver.

What Rideshare GPS Data Contain

Rideshare platforms typically log location data at frequent intervals throughout a trip, not just at pickup and drop-off. This data can show a vehicle’s path, speed, and any stops or detours along the way. The precision and frequency of that data can vary by platform and device. From this data, maps, timelines, and animations of the route are created.

Movement vs. Stopped Time

Litigators often need to know how long a vehicle remained stopped at a particular location. GPS data can establish this with more precision than witness recollection alone, provided the analysis accounts for GPS drift. GPS drift is a phenomenon inherent to many GPS receivers where a stationary receiver can appear to “drift” even when it hasn’t moved. It gives the appearance of movement when, in fact, the receiver is stationary.

Route Deviations

Whether a vehicle followed its expected route, or deviated from it, and for how long, is a recurring question in these cases. A short deviation might be explained by traffic, a detour, or simply a missed turn. A longer or more unusual deviation raises different questions. Distinguishing between the two requires comparing the actual GPS record against what a typical route for that trip would look like.

Unlikely Dropoffs

A passenger’s ride receipt can show when a driver indicated that a dropoff occurred and the trip ended. Comparing the dropoff time to the GPS record can help determine how likely it was that a dropoff actually occurred. For example, was the vehicle traveling at 30 mph at the time of the dropoff? If so, it’s likely that the dropoff didn’t actually occur, or this could indicate errors in the GPS record. This is why it’s important to retain an experienced engineer to review the record.

Where This Data Gets Misread

A common mistake I see in rideshare GPS analysis is treating raw location points as if they were perfectly precise, when GPS data always carries some margin of error. A device that appears to have suddenly jumped 50 feet in one second in an urban environment surrounded by tall buildings may not have moved at all. This is a well-documented GPS accuracy limitation in urban settings, and may or may not be evidence of movement. Getting this distinction right, and being able to explain it clearly, is often the difference between an analysis that holds up and one that cannot be supported under cross examination.

Another common mistake occurs when a route includes back tracking over previously traveled roads. It’s difficult to show this type of movement on a static route map. I create animations that clearly show the route traveled over time, regardless of how complicated the route was.

Why This Analysis Requires an Engineer

Reading a GPS track accurately requires understanding how GPS technology actually works: satellite geometry, signal degradation in urban canyons, and the accuracy limitations inherent in the GPS system and consumer-grade GPS chips. I bring a graduate-level telecommunications and wireless engineering background to this analysis, along with a Six Sigma Master Black Belt in the quality sciences, which means I can quantify the uncertainty in a GPS track rather than simply asserting a conclusion.

Errors can be introduced into the GPS record through common processing and RF propagation phenomena, such as multipath interference, signal reflections, drift, satellite constellation geometry, temporal and spatial gaps, and processing delays.

My blog titled What GPS Records Can and Cannot Prove in Litigation provides more detailed information.

It’s important to have an engineer with the right education, training, and experience in these topics interpret the GPS evidence in your case.

How I Approach These Cases

  • Data acquisition and review. I request and review the GPS logs and other related materials for the trip in question.
  • Accuracy assessment. I evaluate the precision of the underlying data, including the device type, logging frequency, and environmental conditions that affect GPS accuracy.
  • Mapping and timeline construction. I create clear maps and timelines showing the vehicle’s movement, speed, gaps, and any stops.
  • Report and testimony. When requested, I compile my analysis in a thorough report which can be read and understood by non-technical readers. My testimony holds up because the underlying methodology is sound, and I am experienced at providing clear, meaningful, and defensible testimony at deposition and trial.

Why Attorneys Retain Me in These Cases

  • High case volume in this specific area. Rideshare and app-based GPS litigation is one of the more frequent case types in my practice.
  • I don’t work for rideshare platforms. I have no conflict of interest. I’m retained on these cases by the passengers’ or claimants’ attorneys.
  • Rideshare testimony experience. I’ve testified in depositions and in court on GPS location records in many rideshare cases on behalf of plaintiffs. I’ve been involved since the initial Lyft and Uber bellwether cases. I’ve also been retained and testified in JCCP cases in state court, as well as Multi-District Litigation (MDL) in federal court.
  • Decades of experience. I’ve been analyzing and mapping GPS location data since the early 2000s, long before GPS was built into mobile phones and other devices. I’ve stayed current with the current technology and capabilities of GPS receivers in modern smartphones.
  • I’ve never had an opinion limited or excluded. No Daubert challenge has ever succeeded against me; my GPS methodology has held up consistently across contested matters.

Frequently Asked Questions

How accurate is GPS data from a rideshare app?

It can vary by platform, device, and environment. Consumer-grade GPS receivers, like the one in a smartphone, are generally accurate to within three meters under open-sky conditions. But that accuracy can degrade near bridges, mountains, in cities, tunnels, and indoor environments. My analysis accounts for that variability and provides clear explanations of accuracy and uncertainty.

Can GPS data prove a vehicle was stopped versus just moving slowly?

Usually, yes, with the right analysis. Distinguishing genuine slow movement from GPS drift on a stationary vehicle requires looking at the pattern of points over time, not just the raw speed coordinates. When speeds aren’t provided in the records, I compute them based on the distance between adjacent GPS points (using the Haversine Formula) and the time difference between them. When the platform does provide speeds, I verify them and report relevant discrepancies.

Do rideshare platforms retain this data for very long?

Retention periods vary by platform and are worth confirming early in a case, since the underlying data needs to be requested and preserved before it’s no longer available.

What if there are gaps in the GPS record?

GPS data can have gaps in location and time. I flag relevant data gaps explicitly in every report and provide analysis on whether the source or cause of the gaps can be determined.

If your case involves GPS data from a rideshare or delivery platform, I’d welcome a direct conversation about what the data can and can’t establish.

Talk to Mark about your case →

Ready for an expert opinion? Get in touch today!

Mark McFarland, PE, is a forensic electrical and telecommunications engineer in Boulder, Colorado. He spent twenty-one years at the federal telecom research lab before founding Discovery Engineering in 2015, and is retained nationwide by plaintiff and defense counsel in civil and criminal matters.

Discuss Your Case
Like this article? Spread the word!
Related Posts

How Cell Tower Sector Data Can Show Where a Phone Actually Was

Cell tower and sector data can show where a phone was, or wasn't. Learn how the analysis…

What GPS Records Can and Cannot Prove in Litigation

GPS evidence isn’t infallible. Learn what GPS records can and cannot prove in litigation,…

How Gas Detector Alarm Design Can Fail Workers in Confined Spaces

How gas detector alarm design, silenced alarms, and sensor errors can fail workers in…