Movement data

Mobility data describes how people and vehicles move between places: trip volumes, origins and destinations, travel modes, times and routes. Transport planners, cities, tourism boards, logistics firms, retailers and researchers use it to plan infrastructure, model demand, understand catchment areas and measure the effect of events or policies.

Typical fields:

• Origin and destination zones
• Date, hour and day type
• Trip counts or estimated travelers
• Travel mode: walking, car, public transport
• Trip purpose or segment, where modeled
• Distance and duration
• Visitor type: resident, commuter or tourist
• Panel size and expansion factor

Sources and collection

Mobility datasets are built from aggregated mobile network data, consented app location panels, connected vehicles, transit smart-card systems, road sensors and travel surveys. Raw signals are converted into trips, assigned to zones and scaled to the population. Telecom-based data covers many people but locates them coarsely; app panels are more precise but smaller.

Delivery and pricing

Delivered as origin-destination matrices, time series by zone and dashboards, via files or APIs. Pricing is usually per study area and period, or an annual licence by region, granularity and refresh frequency.

Privacy

Mobility data must be aggregated so that individual journeys cannot be reconstructed. Zones should not be too small, low counts should be suppressed, and device-level trails should never be delivered.

Before you buy

• Ask about the source, panel size and expansion method.
• Check zone sizes and suppression thresholds.
• Compare outputs with known counts, such as traffic counters or ticket data.
• Confirm how travel mode and trip purpose are inferred.
• Review anonymization and aggregation documentation.