Where people move, between any two places
Aggregated movement flows that show how many trips and devices go from one area to another, by date and hour. Built on H3 hexes, so you can measure movement at a consistent grain anywhere.
Movement, counted between areas
Origin-destination data measures how people move across a region. For each pair of areas, on a given date and hour, it records how many trips were made and how many distinct devices made them. Areas are defined as H3 hexagons, a consistent global grid, and each flow also carries readable origin and destination region and city labels, so you can read movement between neighbourhoods, cities, or regions.
Origin, destination, time, and volume
Origin
Origin region, city, and H3 hex, so you know exactly where a movement started.
Destination
Destination region, city, and H3 hex, pinning down where the movement ended.
Date and hour
Every flow is stamped with a trip date and hour of day, so patterns show by time.
Trips and devices
Trip count and device count, separating total volume from the number of distinct people.
Search a place, see where its movement goes
The live catalog lets you search by origin or destination place and filter by country, origin and destination region, and city. Preview the flows, then export the pairs you need, delivered as a file, by API, or through Polygon AI.
What teams do with movement flows
Catchment and trade area
See where a store's visitors actually travel from, and how far a location really pulls.
Commute and demand
Map commuting patterns and demand between areas to plan routes and services.
Connectivity
Understand how well connected a site is to the places its users come from.
Visitor origins
Trace where visitors to a city or attraction arrive from, and when.
Mobility and policy
Study movement between neighbourhoods to inform infrastructure and policy.
Migration and change
Track how flows between areas shift across dates and hours over time.
Consistent, readable, and joinable
Because flows use the H3 grid, movement is measured the same way everywhere, and because each hex carries city and region labels, the data reads in plain terms and joins cleanly to xMap POI, footfall, and traffic data.
H3 grid, everywhere
A single global hex system, so origin and destination areas are comparable across regions.
Trips and devices
Both total trips and distinct devices, so you can separate volume from reach.
Date and hour
Time-stamped flows reveal commute peaks, weekends, and change over time.
Flexible delivery
Catalog export, API, and plain-language querying with Polygon AI.
Origin-destination data, answered
What is origin-destination data?
Origin-destination data measures movement between areas. For each pair of areas, on a given date and hour, it records how many trips were made and how many distinct devices made them, so you can see where people move and when.
What fields come with each flow?
Each flow includes the country, trip date, and hour; the origin region, city, and H3 hex; the destination region, city, and H3 hex; and the trip count and device count.
What is an H3 hex?
H3 is a global grid that divides the world into consistent hexagonal cells. Using it means an origin or destination area is defined the same way anywhere, which makes movement comparable across cities and regions.
What is the difference between trip count and device count?
Trip count is the total number of trips made between two areas, while device count is the number of distinct devices that made them. Together they separate overall volume from the number of individual people moving.
How granular is the data?
Flows are reported at the level of H3 hexes and by hour of day for each trip date, so both spatial and temporal patterns are visible.
How is the data delivered?
Search and preview in the catalog, then export the origin-destination pairs you need as a file, pull them by API, or query them in plain language through Polygon AI.
Follow the movement between any two places
Explore the live flow catalog, or tell us the origins, destinations, and time windows you need.