Had I not used the '-fn' option, files would have been identified with a column 'file' which contained the file name. This plots all of my files from January 2011, identifying each file with a column 'fn'. % fit_to_cols -fn /media/GARMIN/Garmin/Activities/2011-01-*.fit This plots data directly off my Edge 500, which is plugged into the USB port. % fit_to_cols /media/GARMIN/Garmin/Activities/-16-20-25.fit This plots data from a FIT file stored in my GoldenCheetah data directory. I avoid Windows whenever possible.Īn example, where '% ' is the command prompt, and where it is assumed 'fit_to_cols' is in the execution path: On Linux, simply save the file, make sure it has executable permission, then run it in the standard Linux fashion. When importing the CSV, make sure spaces and not commas are selected as the delimiter.

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. 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.

So I wrote a script, fit_to_csv, to create a readable table from FIT data. However, to help with that work, I needed a way to quickly plot the data in a FIT file. I've been working on a code to filter motorized segments from FIT files, using Kiyokazu Suto's Garmin::FIT package for Perl.

Converting .fit to .tcx