I've been working on a code to filter motorized segments from FIT files, using Kiyokazu Suto's Garmin::FIT package for Perl. However, to help with that work, I needed a way to quickly plot the data in a FIT file. So I wrote a script, fit_to_csv, to create a readable table from FIT data.
The code produces a space-delimited file with each column describing a field either contained in the FIT file or derived from data in one or more fields of the FIT file. I have a series of scripts for handling such files and generating plots from them, or they can be trivially loaded into a spreadsheet like oocalc or even Excel, or almost any other plotting package, using the "CSV" format. When importing the CSV, make sure spaces and not commas are selected as the delimiter.
The code's available here.
On Linux, simply save the file, make sure it has executable permission, then run it in the standard Linux fashion. On Windows, well, you're on your own. I avoid Windows whenever possible.
An example, where "% " is the command prompt, and where it is assumed "fit_to_cols" is in the execution path:
% fit_to_cols ~/Library/GoldenCheetah/djconnel/2010_11_14_10_13_04.fit
This plots data from a FIT file stored in my GoldenCheetah data directory.
% fit_to_cols /media/GARMIN/Garmin/Activities/2011-01-01-16-20-25.fit
This plots data directly off my Edge 500, which is plugged into the USB port.
% fit_to_cols -fn /media/GARMIN/Garmin/Activities/2011-01-*.fit
This plots all of my files from January 2011, identifying each file with a column "fn". Had I not used the "-fn" option, files would have been identified with a column "file" which contained the file name.
% fit_to_cols -h
This prints help information.
The major weakness of the code is it assumed fixed data in the FIT file. FIT is a lot more sophisticated than this: the data can vary from device-to-device. I've hard-coded my script with the data I'm most interested in from my Edge 500. Honestly I'm still trying to figure it all out.
After I'd gotten a functional version of this code together I found someone else had done something similar: fit2csv.pl. I think my code is somewhat more sophisticated than that one, since the latter assumes a particular order for data fields to be stored (I use the hash tables to look up the order) and it doesn't handle undefined values well. My code also allows for multiple files to be listed at once and has several derived parameters like dx, dy, and r.
Thanks to Kiyokazu Suto for doing such nice work on Garmin::FIT.
Rides to Remember
2 hours ago