From Geography To Similarity
Conceptual OverviewAn S2 Cell
A geographic unit in the supported dataset.
330 Dimensions
A learned embedding for the cell.
Similar Areas
Compare embeddings to identify areas to investigate.
At A Glance
- Provides: Geographic embeddings for similarity analysis and model development.
- Not: Raw searches, individual movement records, or validated business predictions.
02 / What's Inside
Three Source Blocks, One Learned Representation
Feature ablation can compare a block’s contribution under your evaluation design. It does not by itself establish why a location performs well.
Built For Power
- one embedding per covered geographic cell for similarity analysis
- known source blocks; individual dimensions remain abstract
Kept Private
- no raw search queries or device-level mobility traces
- no individual-level data of any kind
03 / Data & Schema
Join Your Locations To Geographic Cells
Key Facts
- geo_id is an S2 cell token; convert point coordinates to the matching level and string representation
- Administrative-area identifiers are Google Place IDs; do not confuse a cell with an individual POI
- Use the subscribed dataset’s actual coverage and version; a missing cell is not evidence of no activity
04 / Example Query
Compare Similarity, Then Investigate
Synthetic identifiers and scores; exclude the target cell
WITH target AS ( SELECT geo_id, features FROM `YOUR_PROJECT.population_dynamics___us.v1_s2_z12` WHERE geo_id = '80ead45' ) SELECT t.geo_id, ROUND(1 - ML.DISTANCE(t.features, x.features, 'COSINE'), 3) AS similarity FROM `YOUR_PROJECT.population_dynamics___us.v1_s2_z12` AS t CROSS JOIN target AS x WHERE t.geo_id != x.geo_id ORDER BY similarity DESC LIMIT 4
Illustrative output · No request executed
| geo_id | Similarity |
|---|---|
| example_cell_a | 0.921 |
| example_cell_b | 0.904 |
| example_cell_c | 0.896 |
| example_cell_d | 0.881 |
Rankings can change when the feature block changes
WITH sliced AS ( SELECT geo_id, ARRAY_SLICE(features, 0, 127) AS search_block FROM `YOUR_PROJECT.population_dynamics___us.v1_s2_z12` ), target AS ( SELECT geo_id, search_block FROM sliced WHERE geo_id = '80ead45' ) SELECT s.geo_id, ROUND(1 - ML.DISTANCE(s.search_block, t.search_block, 'COSINE'), 3) AS similarity FROM sliced AS s CROSS JOIN target AS t WHERE s.geo_id != t.geo_id ORDER BY similarity DESC LIMIT 4
Illustrative output · No request executed
| geo_id | Similarity |
|---|---|
| example_cell_e | 0.933 |
| example_cell_b | 0.919 |
| example_cell_g | 0.907 |
| example_cell_h | 0.894 |
05 / Analysis Modes
Choose An Analysis And Its Validation
Cluster labels are analyst interpretations. Validate them against independent context; the vector does not provide demographic or lifestyle labels.
06 / Use Cases
Use Embeddings As Evidence To Test
Potential applications include retail, public health, and planning. Validate each application against its own outcomes and constraints.
Industries
07 / Privacy And Explainability
Separate Representation From Explanation
Privacy-safe By Design
- No raw individual search histories or device-level movement records
- The embedding represents an area, not a person
Bring It To Life
- Use Places Insights or other documented context to describe an area
- Keep interpretation, prediction, and validation distinct
330 latent features for a covered geographic cell
A similarity score for a defined vector comparison
Independent, dated geographic facts that help interpret the result
Observed outcomes and held-out testing for any predictive claim
Similarity alone does not establish demand, causality, or future performance.
08 / Vs. Places Insights
Two Different Questions, Two Different Answers
| Dimension | PDI | Places Insights |
|---|---|---|
| Representation | Learned geographic patterns | Structured attributes of places |
| Shape | 330-dimensional vector per cell | Named fields; governed query outputs |
| Geography | S2 cell; area varies geographically | Place-level source, constrained outputs |
| Interpretation | Latent features; not named measures | Fields such as type, rating, and hours |
| Typical Use | Similarity exploration and ML features | Place counts, mix, and aggregate analysis |
| Access Rules | Check the country listing and terms | SQL threshold; separate count-function rules |
| Prediction | Requires a separately validated model | Requires outcomes and a validated model |
The pairing is the point: PDI finds where to look, Places Insights explains what's there once you've found it.
09 / Coverage And Access
Select The Country Dataset And Verify Coverage
Coverage
- Country-specific datasets share the documented embedding schema
- Check cell availability and geographic alignment for your use case
Access
- Follow Google’s current signup and cloud-setup instructions
- Budget for applicable dataset access and BigQuery usage
Recheck country availability and launch-stage terms before quoting or committing to an implementation.
Choose an available country listing.
Link the dataset and map your coordinates to cell tokens.
Check coverage, compare a baseline, and validate the intended use.
Conceptual diagram

