Consolidation and analytics of personal data has long been an interest of mine, particularly sports tracking like cycling and running. Mobile devices are making this easier, and every day new services allow access to all kinds of data which up to recently would have to be recorded manually (and therefore just not done, well except for people like Nicholas Felton).
However, for particular kinds of events, such as going to the gym, I have been taking the time to enter them manually in Google Calendar, into a special calendar set up to record just fitness events. I have always wanted to store other fitness items on the same calendar for easy visualisation of all fitness activities, but it was always too hard.
Since I have moved all of my running and cycling to Strava now, I decided to implement an application to sync my Strava activities to my Google Calendar (i.e. Strava-to-Google Calendar synchronisation). The solution works quite well, and I am guessing if I find it useful then there will be someone out there who might also like access to it.
x2G (x-to-Google) first connects to your Google Calendar account, and then lets you connect Strava as well. Once both are connected, you choose the calendar you wish to sync your activities to, and hit the “Quick Sync” button. Full Sync will clear out all of the strava entries on the calendar before the sync (it wont delete anything that is not strava related).
Right now, it is in beta and still running on Heroku, so the URL will change in the future, but if you would like to test it with me feel free. Also, since it is in beta, I recommend connecting to a dedicated calendar rather than your primary calendar (just in case there are bugs).
It is called ‘x-to-Google’ because I am not stopping at only Strava. I have also got a Moves connection working as well, so expect that in the near future.
Any feedback either through this blog or email to: firstname.lastname@example.org.
Update 15-Sep-2014: Sorry everyone if you have been having issues, I pushed an unfinished version up to the site and it was causing issues. I have fixed it now.