Custom Query (49 matches)

Once we have the workouts storage ready (#4), we will need a way to upload gps tracking information to the system, either to an existing workout or (used more often) to create a new workout based on that gps tracking information.

First we have to define which kind of files we will allow (gpx, tcx, fit, etc) and then decide how we will store them: save the files "as is", parse them and save the parsed data into the db (maybe keeping the original file around).

This is directly related to the way we will show data on a map (what kind of files do we need for that, for example, if we are going to use a static file to provide the info when rendering the map).

Once some tracking information has been uploaded, some of that information should be "modifiable" using the workouts editing UI (#4) (we still have to define which info exactly).

Open question: How should we deal with incorrect file uploading? That is, I decide to upload a gps tracking file to a workout, but then I realize that I had chosen the wrong file. How could I fix it?

1. Remove workout, re-upload file and create new workout

2. Upload new file on the existing workout, overwriting existing data

3. (put more options here and let's discuss about it)

Kind of:

• You did XX kms this week, climbed XX meters and cycled XX faster/slower than last week (average)

• You did XX kms running, XX kms cycling, XX meters swimming

• Last month you had no activity

• etc

All kind of crazy stats you can think we can get out of the workouts, put both in the workouts detail page (a hint on the stats, maybe) and a full stats page for all workouts for the given user (maybe with filters by date, activity, distance, time, etc)

Our code supports GPX files when adding/updating a workout.

We should support .fit files too (like the ones exported by garmin devices).

Some resources:

​https://github.com/dtcooper/python-fitparse

​https://github.com/K-Phoen/python-fitparse