Skip to main content

Convert Strava activity to a Strava route: the two 'official' methods

3 min read

This post is written in response to queries from my local cycling group as to how to convert Strava activities to Strava routes.

Both methods are not always entirely reliable and have limitations (see below). Method One is the easiest and simplest.

Method One (via the 'standard' Strava website):

Follow the instructions here

Screenshot

Method Two (via the Strava labs website):

Screenshot

Instructions:

1. In your browser, open the Strava activity you want to export. It will be in the format https://www.strava.com/activities/1234567890

2. Copy that link to your clipboard

3. Open the Strava Labs 'GPX to Route tool here

4. Paste the link in to the tool and then click 'Convert'. (The first time you do this you will be asked to link Strava Labs to your Strava. This is fine as both websites are run by Strava.)

If you get an 'Error Computing Route' message, you can either try again later (occasionally waiting will work) or more usually you have to give it up as a bad job! (There are online and offline tools for advanced users that can sometimes help.)

Exporting routes to GPS devices:

Once your route has been converted intro Strava using either method, you can then export it as a GPX or TCX file for importing into your device.

N.B. If you have a newer Garmin device - e.g. Edge 520, Edge 1000 - you can cut this step out by installing the Strava Routes Connect IQ app and downloading the route direct from your device.

Limitations:

Both methods do not allow you to easily edit your routes, if at all. So if you went the wrong way on your activity, the route will go the wrong way as well. Or if you want to simplify your route, perhaps by taking a more direct route, you will probably not be able to.

There are also map limitations in the converter. If it can't find a valid route on the Strava basemap then it will route a longer valid way around - even if your activity went the shorter way!

For these reasons I rarely use either of these methods, preferring to create my Strava routes from scratch via the Route Builder tool. (There are also ways of doing routes via non-Strava websites, e.g. RideWithGPS, but that's outside the scope of this post.)

Summary: if you're happy with the limitations and don't mind route imperfections, then by all means use these methods. But if you're a perfectionist like me, these methods will not be for you!

First posted: 1 October 2017
Last updated: 1 October 2017

Indieweb for end-users - some thoughts

3 min read

I've been mulling over this post by this post by Jeremy Cherfas , my reply and then Chris Aldrich's response asking for views on what the could do better.

My attraction to the IndieWeb has been about owning my data, avoiding silos where possible (i.e. where the friction is tolerable), and federalising content. (You can read a little about my journey on my IndieWeb user page .) I only came across the definitions of IndieWeb Generations the other day, but would label myself as a Gen2 with a little bit of Gen1 thrown in for good measure.

I've had a Known instance since 2014 with varying degrees of success with POSSEing and so on, but to be honest my focus has often been more on the 'own your data' side of things. I've needed to nudge myself to get back on track with Known and stuff.

Whilst I'm a geek I generally feel a fish out of water by the more techical content of the IndieWeb site and the conversations in the IRC chat room . There's probably a few relatively simple things that could be done to improve things, as others replying to the original post have already mentioned (easier onboarding, more user-friendly documentation, more approachable look-and-feel, etc.). Also perhaps an IRC sub-chat room for beginners (or, dare I say, some sort of more modern forum where Q&As can be asked in non-real time?). And whilst I prefer text instructions myself, a lot of people prefer videos so how about some tutorial videos?).

Here's an example from the Gen 2 bit of the Generations page:

 

What if this said something like:

Understand basic concepts of posting content on your site that's also copied elsewhere, replying to posts on others' sites from your own, and using online free tools to make this work seamlessly

(Wording not definitive; just to illustrate how simpler wording could help newer users.)

I'd also like to mention Homebrew Website Clubs. I was really attracted to these when I first knew about the IndieWeb, but have never actually been to one. The impression I got is that they were more for coding and developing than helping end-users to improve their own websites, incorporate blogging, etc. I think I'm wrong (and am very glad to be!), but do we always present an inclusive 'all levels of experience welcome' approach?

None of this is intended to sound ungrateful for what we've got and where we are now - quite the opposite. Without the highly-skilled and commited developers we have, and the shared vision of IndieWeb, we wouldn't have anything to talk about improving (we'd be oblivious in our walled gardens!). I am massively grateful for the work and efforts of the IndiewWeb community, and only want to help us collectively improve and attract others to join.