Bulk export of WKO data to CSV

liversedge

Hi Everyone,

After a couple of months of intense activity and testing I am now releasing my wko to csv converter to the world. Pre-compiled binaries for Windows, Linux and OS X are available and the program has been tested on over 1,200 files from users of Powertap, SRM, Garmin, iBike, Ergomo, Polar, Computrainer and Velotrons and it succesfully extracted all graph data from all files parsed.

It is an open-source command line tool and available from https://sourceforge.net/projects/wko2csv

I do hope you find it useful, and if you find it doesn't work for your files then pm me and I'll take a look.

Thanks,
Mark

Alex_Simmons/RST

I haven't tried it yet, but I will before too long. I just hope I can understand how to make it work properly on my machine.

Assuming all is well, then this will be an awsome tool and we salute you for doing it.

As much as I like WKO+, encourage people to use it and occasionally provide input to the developers, it is good to know that many years of data across dozens of athletes can be re-stored in non-proprietary file format.

two thumbs up

Silly questions (since I've not got time to fidle with it right now):

1. Does it create csv files in the original format native to each power meter?

2. What does it do with the extra data in a wko file (e.g. rides notes etc)? Or have I forgotten which data is stored in the calendar.dat file and what's in the wko files?

liversedge

There is the rub.

It creates a CSV file with exactly the same graphs that the WKO file has, so if you have a workout with only HSA then you'll just get heartrate, speed and altitude in the corresponding CSV file. If its from an iBike and you have PHSDAW^ then you'll get a CSV file with Power, Heartrate, Speed, Distance, Altitude, Windspeed and Slope.

It will output samples at exactly the same intervals as the device originally recorded it, and as it is stored in the WKO file, but I always add a time column. I'm adding a feature to specifiy specific columns (and have null values for columns that don't exist in the source file) and column headings so you can make an output that 'looks' like other file formats and export all files to it in one hit.

The workout settings like date, duration, athlete name etc are not supported by CSV formats. I'm thinking it would be good to output as some kind of XML, perhaps the WKO pwd.xsd. I'm looking at encoding the filename with athlete name, workout code and date.

Lastly, the point here was mostly about unlocking their proprietary format for others to read. I hope that software producers can re-use my findings to allow them to read WKO files directly in their software.

You'll see on wattage that there are a couple of minor bugs - I'll be fixing those today.
EDIT -- NOW FIXED.

Thanks for the positive feedback! 8)