LyftManjunath ShettarProblem & solution
Refreshing the Travel-Time Map Behind Lyft’s Marketplace: Rebuilding Neighborhood Reachability…
Summary
Lyft’s Neighborhood Reachability Signals dataset supplies precomputed travel-time estimates between geohash-6 cells and a vocabulary of usable cells for pricing, driver heatmaps, and marketplace features. Production ETAs had remained largely based on 2018–2019 data, systematically underestimating travel times and omitting genuinely matchable pairs, while consumers maintained separate allowlists and denylists. The FORTOP team redesigned the Airflow-generated files by rebuilding the geohash universe from demand and supply history, estimating dense pairs from trip history, using Routing Simulation System (RSS) fallbacks for sparse pairs, and blending partial observations. In the second half of 2025, the refreshed dataset was adopted by Pricing after validation, with reported improvements in accuracy and completeness, a six-month refresh cadence, and plans for nine time-category files per region to represent traffic patterns.
Context
The production dataset’s core ETAs were largely frozen at 2018–2019 levels. It systematically underestimated travel times and omitted genuinely matchable demand–supply pairs, while its geohash universe could include cells that were not drivable. Downstream teams compensated with separate allowlists and denylists.
Approach / What changed
FORTOP rebuilt the Airflow-generated dataset by narrowing candidate geohashes using demand and supply history, estimating sufficiently observed pairs from historical trips, using Routing Simulation System (RSS) estimates for sparse pairs, and blending partial history with simulation. The redesign also established a six-month refresh cadence and plans time-category-specific files.
Takeaways
The legacy geohash universe could include non-drivable cells, including cells over open water in the SFO region, while excluding pairs that were physically close enough to match.
Pairs with fewer than a handful of observations use Routing Simulation System estimates that incorporate traffic conditions; partially observed pairs receive a weighted blend of historical and simulated ETAs.
The planned time-aware version uses nine files per region, allowing consumers to load the current hour-of-week category while keeping read latency roughly flat at the cost of a couple of extra gigabytes of memory.
Source and freshness
- Source
- eng.lyft.com
- Published
- Added to Yomu
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.