Data format

Mapbox Movement datasets cover two different date range types: Daily and Monthly. Multi-month aggregations are also possible.

Quadkeys

Tiles are based on quadkeys. A quadkey is a numeric reference to a geographic partition at a specified OpenStreetMap zoom level. To do additional geospatial manipulation on quadkeys, you can use the mercantile library. The conversion is necessary only if there is a need to convert CSV filenames to geographical regions, since each line item is already converted to longitude, latitude coordinates. You can also use the What the Tile interactive tool to visualize the quadkey locations.

The quadkey data are aggregated at zoom 18, which is roughly the size of a city block (approximately 100 meter resolution). In the dataset, the bounds field provides the outer corner coordinates of each quadkey, while the xlat and xlon fields show the centroid of each quadkey.

Mapbox Boundaries

For Movement data joined to Mapbox Boundaries, the data set contains only the code of the corresponding area in the geography field. This is the last five characters of the ID for counties, and the last three characters of the ID for states is the region’s FIPS code. You can also request that additional Mapbox Boundaries files be provided with a mapping between regional codes and corresponding polygon shapes, coordinates, and surface areas.

Normalization

The activity index is not normalized by area or population density, so larger and denser counties will show higher activity levels. We recommend running additional normalization if the purpose of the analysis is to compare counties or states to each other.

Daily

Device activity is aggregated every 24 hours and generated daily, which allows for frequent updates to reflect immediate changes in activity levels.

FieldDescriptionExample
geographyFor tile aggregation:
Z18 quadkey ID

For Mapbox Boundary polygons:
County ID
State ID
032001323000312110


USA212097
USA147
xlonLongitude of the center of the bounded area (tile only)-122.428207397461
xlatLatitude of the center of the bounded area (tile only)47.6880413955171
boundsThe lower left and upper right corners of the bounded area (tile only)-122.42889404296875, 47.68757916850813, -122.42752075195312, 47.68850362252605
activity_index_totalNormalized activity factor (for all activity types)0.069267
agg_day_periodThe date, in local time2020-01-01

Monthly

Device activity is aggregated over a one-month time window, which allows for periodic updates to reflect changes in typical activity patterns. Multi-month aggregations may be provided for improved coverage and consistency (3-month, 6-month, and 12-month).

FieldDescriptionExample
geographyFor tile aggregation:
Z18 quadkey ID
032001323000312110
xlonLongitude of the center of the bounded area (tile only)-122.428207397461
xlatLatitude of the center of the bounded area (tile only)47.6880413955171
boundsThe lower left and upper right corners of the bounded area (tile only)-122.42889404296875, 47.68757916850813, -122.42752075195312, 47.68850362252605
activity_index_totalNormalized activity factor (for all activity types)0.069267
activity_index_drivingNormalized activity factor (for driving activity) Only available in select markets.0.071023
agg_day_periodFor seven-day:
An integer that describes the day of the week, starting with 0 for Monday

For weekday/weekend:
An integer that describes whether the day is a weekday or a weekend
0 for Monday, 1 for Tuesday, 6 for Sunday



0 for a weekday, 1 for a weekend
agg_time_periodFor hourly:
An integer between 0 and 23 that describes the hour of day

For four-hour dayparts:
An integer between 0 and 5 that describes the index of the four-hour window
4 (4:00 AM)



0 (the 00:00-3:59 time window), 5 (the 20:00-23:59 time window)
Was this page helpful?