Dealroom locations
Every location Dealroom tracks, from continents to metro areas.
Type words to match names, aliases, IDs, types and the places above a location. Press Enter to open the first match, or ArrowDown to move into the list.
Loading Dealroom locations…
Built from the location table as it stood on 3 November 2026.
What this is
Every row of Dealroom’s location table, 61,760 locations from continents to cities, shown as a tree with the same IDs as the Dealroom API. The table says which cities belong to each metro but gives no boundary. This page draws one, so wrong links show up on a map instead of in a wrong number. Nothing here is written back to the table.
The tree
Each location sits under its narrowest parent: city, metro, state, country, continent. All links come from the table. Two metros the table links to each other show as “Shares territory with”, because the table does not say which contains the other.
Figures and partners
Figures come from Dealroom’s ecosystem index and match the site’s ecosystem pages. Only the 662 locations with a profile have them. A region without its own figures shows the sum of its countries. The Ecosystem partners filter marks the places Dealroom’s ecosystem platforms cover.
Boundaries
Each metro is drawn with the area an ecosystem developer there would call theirs. The first of these that exists is used:
- The outline its ecosystem platform draws, if it holds most of the metro’s cities.
- US metros: the Census metro area holding most of its cities. Broad US regions: whole states.
- Elsewhere: the government areas its name points to, chosen by hand. Greater London is Greater London.
- Otherwise, the OpenStreetMap boundary matching its name, or the areas its cities lie in.
The Boundaries tab gives the reason for each metro.
States, provinces and prefectures use their official boundary from OpenStreetMap or the US Census. Where an ecosystem platform covers a state, its outline is used only if it covers at least 90% of the state’s land.
Dots and checks
Dots use the table’s coordinates, or an OpenStreetMap lookup where those are missing (hollow dots). Coordinates that land in the wrong country are not drawn. Red dots lie outside the metro’s boundary, purple ones inside it but not in the metro, orange ones far from the metro’s other cities. The Data checks tab lists them for curators. It changes nothing.
Files
- boundaries.geojson: every boundary below country level, keyed by location ID.
- boundary-check.csv: cities that disagree with their metro’s boundary.
- atlas-data.json: the tree as this page reads it.
How to rebuild it and load it into BigQuery: docs/reference/LOCATION-ATLAS-PREVIEW.md.