Google details how it uses deep learning, Street View imagery to update Maps; open sources TensorFlow model for image text extraction
Posted by Julian Ibarz, Staff Software Engineer, Google Brain Team and Sujoy Banerjee, Product Manager, Ground Truth Team
Context & Ripple Effects
This post is a mid-point in a deliberate arc: after open sourcing TensorFlow in late 2015 and building the Tensor Processing Unit for it, Google is now showing the framework doing revenue-relevant work — reading business names, signs, and opening hours out of Street View imagery so the Ground Truth team can update Maps without manual edits.
It also previews where Maps was headed: the same Street View-plus-aerial fusion later surfaced as Immersive View in 2022, and by AlphaEarth Foundations in 2025 Google was unifying petabytes of Earth observation into maps generated on demand. The 2017 post is the first public look at imagery-as-inference-input replacing hand-curated map data.
First-order effects
- Google's Ground Truth team can refresh Maps listings — business names, addresses, signage — directly from Street View passes instead of waiting for owner submissions or manual review, cutting the update lag for millions of places.
- Developers working on document or scene text extraction get a production-tested TensorFlow model for free, lowering the barrier to building OCR-style pipelines on Google's stack.
Second-order effects
- Rival mapping providers (Apple, HERE, OpenStreetMap-based services) face a widening freshness gap they must close with their own imagery-extraction pipelines or licensing deals, since crowd-submitted edits alone cannot match automated Street View sweeps.
- Every open-source release like this one feeds back into TensorFlow's ecosystem position — analysis at the time showed it remaining the platform of choice across mobile and server — pulling third-party ML work onto infrastructure Google controls and its TPUs accelerate.
Third-order effects
- The pattern here — proprietary imagery corpus plus open model plus custom silicon — becomes the template for how map and geospatial products are built: continuous perception pipelines rather than periodic manual surveys, a structure that scales from street-level signage to planetary Earth observation.
- Open-sourcing component models while keeping the data flywheel private establishes the 'open weights, proprietary control plane' dynamic: competitors can replicate the technique but not the Street View corpus that makes it valuable.
The trend: Mapping is shifting from periodically hand-edited databases to continuously inferred products, where a company's proprietary imagery corpus — not its editors — becomes the defensible asset.