Trying to export data from Metroview? You've come to the right place!
*Looking for what's changed for Metroview data exports? Click here for specific update information at the bottom of this page*
To download data, you'll first need to follow the steps in the below GIS Data Export section.
Any data that you have saved will be displayed on the Data page. Before the data is ready to download, the Link column will display "processing..." When the data is ready to download, the Link column will display an orange Download button.
You can sort files by creation date to more easily find what you're looking for. Click the Date Created column header to reverse the order.
Data Fields / Data Dictionary
The exported 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
"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 pairs of columns are provided.
People counts by Gender:
People counts by Age:
forward_average_speed, reverse_average_speed (meters per second)
GIS Data Export
There are two ways to download Streets GIS data from the Metroview platform:
To download data for your entire region, navigate to the Map tab and select Streets on the left side panel. After clicking on Streets, a panel will appear on the right side of the screen, indicating a few statistics for your entire area of interest.
Under the date is an orange Download button. If you haven’t selected any street segments (edges), this will download data for the date range and the entire area of interest shown in the right side panel.
To export data for a different date range, use the time period filter on the left side panel before clicking the download button.
After clicking on the Download button, a screen will pop up in the middle of the page where you can edit the filename and description of the data export.
Then, click on the Save to Data button. This will start the process of creating the data export – a zip file which includes the shapefile for the area of interest and a CSV file which includes the data. You can access this at any time by clicking on the Data tab at the top of the page. (Depending on the size of your area of interest and selected time frame, it may take some time for the shapefile export to finish processing.)
Selected Edges Export
To download data for a few specific street segments (edges), navigate to the Map tab and select Streets on the left side panel. A “Zoom in to load edges” button will appear near the left panel; click this to zoom in and load edges in the extent shown.
Select edges by clicking on the segments you want to export. A panel will appear on the right side of the screen, with an orange Download button below the date range. Now when you click on the Download button, only the selected edges will export (instead of the full area of interest). Edit the time frame by choosing hourly, daily, monthly, or yearly counts for your selected edge(s). Click Save to Data for your export to begin processing. This process may take some time depending on the number of selected edges and time frame. You can download the data at any time from the Data tab.
Working with the GIS Data
When you export GIS data from the Metroview dashboard, you’ll have access to two files – a CSV of data and an Open Street Map shapefile basemap.
To provide the Streets data, we map the Strava activity data onto OSM street and trail segments. We periodically pull new versions of OSM throughout the year, and then run additional processing on it to make it a routable basemap. We run a process that breaks all streets/trails/etc at intersections (decision points) to create Edges. When this occurs, we then need to apply a new ID to each Edge, because one OSM ID may (and likely does) now apply to multiple Edges. These Edge IDs are unique to the Strava data, and are unique to the specific basemap used at the time the data is created.
We have included two ID fields in the shapefile: osmId, which indicates the OSM geometry the segment is a part of, and edgeUID, which is used to join the data in the CSV to the shapefile. NOTE: the data cannot be joined to the osmId field. This is for reference only.
Depending on the time frame you have selected for the export, you may need to do additional filtering of the CSV file before joining it to the shapefile. This there’s a row in the CSV for every time interval (hours, days, months, or years respectively) that an edge had bicycle trips that traversed it. For instance, if you exported daily April 2021 data for Denver County, the CSV will include each edgeUID for every day in April that it had activities, meaning that most edges will appear multiple times in the CSV (and up to 30 times in April).
Similarly, when working with monthly counts, if your file contains more than 1 month of data make sure you filter the data first before joining to the shapefile.
Data Export and Schema Changes
As of May 2021, changes have been made to Data Export functionality and the associated data tables.
Metroview users now have the ability to export hourly, daily, monthly and yearly aggregated datasets. This feature was added as a direct result of the feedback provided by partners and aims to make temporal analysis more efficient. Users will no longer need to add together the daily data to reach monthly or yearly insights. These datasets will be ready to use in your GIS or Data Analysis system with no additional math required.
In conjunction with export changes, there is an updated data structure that can be found when working with the data tables/CSV file.
Noteworthy changes to the tabular data have been highlighted below:
- Hourly columns have been replaced with hourly rows in the CSV file
- Previously present morning/evening columns have been removed from the hourly data. Morning/Evening columns will still appear in the daily, monthly, and yearly data.
- The date column will become hour, date, month, or year depending on the export’s timeframe. The values are ISO 8601 formatted for the appropriate time frame.
If you have scripts in place to ingest, load, or transform Metroview data please review a sample export and take into consideration the aforementioned changes when adjusting your workflows.