Improving Route Reliability for Indian Road Conditions in Google Maps
A Google Maps fix for routing cars into lanes they cannot use, built on a road suitability score
✳The problem they went after
In Indian cities Google Maps sends four-wheelers into narrow two-wheeler lanes, gated communities, roads under construction and private paths. Drivers find out mid-journey, then reverse, U-turn or reroute. The causes named are incomplete road metadata, routing logic that barely segments by vehicle type, and a feedback loop too slow to correct urban infrastructure that keeps changing.
✳What they actually did
The centrepiece is a Car Suitability Score built from road width, vehicle type, telemetry signals such as sudden slowdowns and reversals, and construction probability. Routes below a threshold are avoided by default or surfaced with a warning. Around it sit explicit road width labels, an Avoid Narrow Lanes toggle under route options, and one-tap issue reporting with structured categories like narrow road, unpaved surface and private route. Success is measured by route abandonment, defined as deviating within the first kilometre or U-turning within three minutes.
✳What you can take from it
Worth stealing
- Suitability score blends road width, telemetry and construction data
- Abandonment defined as a U-turn within three minutes
- Guardrails cap added route time below five percent
- Structured report categories replace freeform feedback
Read this if
Defining success metrics for a change to a core algorithm
The transferable bitRoute abandonment could mean almost anything, so it gets pinned to two observable behaviours with thresholds attached. The guardrails do the same job in reverse, holding ETA accuracy steady and capping added route time below five percent so the fix cannot quietly make navigation worse for everyone else.
✳The submission itself
Open the PDF →Reading on a phone? The embedded viewer is cramped — open the PDF in a new tab instead.
