Thanks to everyone that provided feedback on our previous expansion of user data export, we have pushed an update so that it now also supports:
- Heart rate information in exported activity GPX files
- Start/stop in GPX for all activities where the user paused and then resumed their activity
Heart rate information is included with each GPS data point via
gpxtpx:hr tags, while each pause/resume results in a new
We recently made a change to developer Health Graph read access.
Developers can now read data from their own app registering account, the one they listed when they submitted their app registration in the Partner portal, without needing to apply for special Read permissions. This automatic read permission lets one begin using the full Health Graph API immediately against their own data.
To make certain everyone is clear on what the change enables, let’s define “registering account” as the account under which an app is registered. Then as far as permissions are concerned, the new rules for Health Graph data requests are as follows:
- A read request for the registering account succeeds
- A read request for a non-registering account succeeds if and only if Special API Read permissions have been requested and granted
- A write request succeeds
Note: To read from any other Health Graph account, apps still need to make a request for and be granted the Special API Read permissions. Also Health Graph API Policies remain unchanged.
We hope this helps you get going faster on new Health Graph projects.
We have updated the Health Graph user data export capability so that it now supports exporting all activities and all measurements from the user’s account. This includes data written into the Health Graph by partner apps, services, and devices in addition to RunKeeper’s app. Note that for activities which have an associated GPS track, those tracks are exported as well.
For users, this means they can export and backup all their health and fitness data whenever they like. For developers and self hackers, this also means they can download and manipulate their own user data as they see fit. We’ve had a number of requests for the latter, and we’re very glad to answer them!
More details on how the export works:
Initiate the export by logging in to your RunKeeper.com account settings page, scrolling to the bottom, and clicking on the “Export Data” link. Alternatively you can directly access the export form here: http://runkeeper.com/exportDataForm
You then select starting and ending dates for the data you’d like to export, answer the captcha, and submit your request. Assuming you filled out the form correctly, once you click “Export Data” you’ll see a response indicating that your data is being packaged and will be delivered in a few minutes. You will then receive an email containing a link to download your data in a ZIP archive.
The ZIP contains
measurements.csv CSV files containing activity and point measurement data, respectively. You can use any standard CSV tools and libraries to read and modify these files, including loading them into spreadsheets such as the freely available Google Docs (examples below).
GPS tracks are included as GPS eXchange Format (GPX) files, one file for each activity with an associated a track. Please note that the GPX filename corresponding to any given activity is included at the end of that activity’s
cardioActivities.csv row, too. You can step through the CSV file until you find an activity of interest, then use the GPX filename field to jump out to that particular activity’s track.
Here’s an abridged example of a GPX file containing GPS track data for the first entry in the example activities from above:
Another thing to note: The export does not include photos that the user might have uploaded during RunKeeper recorded activities. Our team discussed including photos versus not, and decided not to for the following reason: We believe including them would be redundant at best (since those photos also remained on the user’s phone at upload time) and could lead to very large ZIP file size and download time at worst.
Your feedback on any and all aspects of this would be appreciated. You can reach us via:
- A response to my data export post in the Health Graph discussion group
- A message to our Health Graph Twitter (@HealthGraphAPI), Facebook, or Google+ accounts
- If you find something you believe is a bug, or you have a new user data export-related feature you would like to request, please visit our Support site to search for your issue; if it’s not already filed, please consider filing it.
If we’ve missed anything critical, please let us know.