Analyzing Strava Data: Part 1 – Exporting and Parsing Segments with Alteryx

Data

Analyzing Strava Data: Part 1 – Exporting and Parsing Segments with Alteryx

Are you an avid cyclist who regularly uses Strava to track segments and claim K/QOM? Are you a data fiend that yearns to analyze and manipulate fitness tracker data in Alteryx for visualization in Tableau? Well, now you can! In this two-part series, I’ll detail the process I used in analyzing my recent OK Freewheel journey.

Step 1: Export GPX Files

To begin, export your data into GPX files by referencing this article from Strava. To keep things modular, I chose to export each segment individually for bulk processing in Alteryx:

Individual Export of GPX Files for Alteryx

Step 2: Get Turnt Up!

Fire up Alteryx and point an INPUT DATA tool to your GPX files by using a wildcard search. In this case, I used .OK*.gpx and specified XML as the file format. I also chose to include file names as a field to keep everything organized:

Alteryx Input Data

What you’ll get is a table containing latitude / longitude coordinates, elevation (meters), date, time and file name:

Alteryx > Results – Input Data (1) – Output” src=”/wp-content/uploads/sites/default/files/blog-content/StravaAlteryx3.png” style=”border-width: 0px; border-style: solid;” /></p>
<p>What you’ll quickly notice is that Strava tracks progress at a very granular level (seemingly, every other second). In the interest of keeping data set sizes small, we’ll compress this data set in Alteryx while maintaining data integrity. I’ve attached a screenshot of what my final workflow looked like. Check the bottom of this post for the actual Alteryx workflow, and stay tuned for Part 2 where I showcase how to visualize this data in Tableau!</p>
<p><img decoding=

More About the Author

Jubail Caballero

Delivery Architect
Optimizing Tableau Relational Models With Row-Level Security: Filters In Part two of this series, we covered a method of distillation to reduce data volume and size. However, we need to translate our ...
Optimizing Tableau Relational Models With Row-Level Security: Performance In a previous installment, we kicked off this blog series by materializing our policy and entitlement table and removing all physical ...

See more from this author →

InterWorks uses cookies to allow us to better understand how the site is used. By continuing to use this site, you consent to this policy. Review Policy OK

×

Interworks GmbH
Ratinger Straße 9
40213 Düsseldorf
Germany
Geschäftsführer: Mel Stephenson

Kontaktaufnahme: markus@interworks.eu
Telefon: +49 (0)211 5408 5301

Amtsgericht Düsseldorf HRB 79752
UstldNr: DE 313 353 072

×

Love our blog? You should see our emails. Sign up for our newsletter!