README.md

In jonocarroll/runkeepR: Extract, analyse, and plot Runkeeper(TM) data

runkeepR

Extract, plot, and analyse Runkeeper(TM) data.

Installation:

Assuming the TravisCI badges above are green (i.e. the current build is stable) this package can be installed via

devtools::install_github("jonocarroll/runkeepR")

or

pacman::p_load_gh("jonocarroll/runkeepR")

Usage

load the installed package

library(runkeepR)

You can get a zipped export of your Runkeeper(TM) data from the logged-in settings page on Runkeeper's website, e.g. runkeeper-data-export-12517482-2016-05-20-1550.zip.

Save the .zip file to a directory (e.g. ~/runkeepR-test/) and unzip the contents (mainly .gpx files and a couple of .csv files). Set this directory as your working directory in R.

setwd("~/runkeepR-test/") ## set directory to location of .gpx files

Loading and processing the route information contained in the .gpx and .csv files into a data.frame is as simple as

routes <- load_tracks(".")
save(routes, file="saved_routes.rds") ## save the data to avoid re-processing

The data can be plotted either with ggplot

load("saved_routes.rds")
plot_ggplot(routes, center="Adelaide, Australia", zoom=14)

or leaflet; this plots all paths but is clever about which ones to load depending on the current viewport, so it's faster.

load("saved_routes.rds")
plot_leaflet(routes)

Summary statistics can be viewed

summarise_runs(routes, dashboard=FALSE)

and presented in a shinydashboard

summarise_runs(routes)

summarised either monthly

or daily

Not affiliated with Runkeeper(TM). Runkeeper(TM) logo © FitnessKeeper 2016

jonocarroll/runkeepR documentation built on Feb. 9, 2022, 3:04 a.m.