Commonly used Strava Metro terminology:
Activities - Complete activities as recorded by Strava users.
Trips (Streets Data) - Crossings of a given edge by Strava users. This can include multiple crossings per activity (when a user traverses an edge multiple times, regardless of direction in a single activity)
Commutes - Activities determined to be utilitarian in nature. More information about how we classify commutes here.
Leisure Activities - All activities that are not classified as commutes.
Bike Data - Bicycle data includes the option to view how many rides have been marked as E-Bike rides by the Strava user. This is visible in a dashboard chart, streets data, and data exports. Bike data is often referred to as rides and/or ebike rides.
Pedestrian Data - Pedestrian data includes run (including trail run), walk, and hike data combined into a single dataset. To view the percentage distribution of each activity type, view the dashboard chart or streets data summary windows.
Streets Data - Data Fields / Data Dictionary
The exported Street (edge) level data contains the following columns:
edge_UID – the identifier for the street block
activity_type – the type of activity, e.g. (ride)
*hour/date/month/year* – one row per aggregated time frame
osm_reference_id – refers to the OpenStreetMap (OSM) Way ID associated with that particular edge. In OSM, a way normally represents a linear feature on the ground such as a road, trail, or bike path. Due to the way edges are created for Strava Metro, many edges can have the same osm_reference_id.
"Forward" indicates trips traveling in the direction the street was digitized into OSM (from the first point of the line to the last point of the line).
"Reverse" indicates trips traveling in the opposite direction the street was digitized into OSM (does not indicate wrong-way travel).
"Trip" counts indicate the number of bicycle or pedestrian trips on that edge during the given timeframe.
"People" counts indicate the number of unique people who completed a bicycle or pedestrian trip on that edge during the given timeframe. For instance, 10 people may have completed 30 trips on an edge during the timeframe.
For each row, the following columns are provided.
*Bike Data Only*:
total_trip_count, ride_count (meaning traditional bikes), ebike_ride_count (from Strava activities listed as ebike rides)
*Pedestrian Data Only*:
People counts by Gender:
People counts by Age:
forward_average_speed, reverse_average_speed (meters per second)
Origins and Destinations Data - Data Fields / Data Dictionary
hex_id - Corresponds to the same hexagon in the associated shapefile. Uses H3 Resolution 8.
date - Displays month or year of data, depending on your export selection
origins_or_destinations - data type
activity_types - bicycle or pedestrian (run, walk, hike)
count - total number of activities starting or ending (depending on data type) in the hex
commute_count - count of commute activities
leisure_count - count of leisure activities
morning_count - 5 am to 10 am
midday_count - 10 am to 3 pm
evening_count - 3 pm to 8 pm
overnight_count - 8 pm to 5 am
weekday_count - Monday to Friday
weekend_count - Saturday and Sunday