Hi, I'm the author of the strava-map-switcher[1] browser extension and last year I published strava-offline[2], a tool to download activities metadata from Strava into local sqlite database (and optionally also activities as gpx).
I'm quite a data nerd, so I wanted to track component wear in more detail than Strava allows. Some people on /r/Strava suggested their online web-based gear trackers, but I was always afraid of trusting them with all the data, and also quite reluctant to enter hundreds of components manually. I really prefer to keep this in git rather than in a 3rd party website that can go away. So now that I have activities metadata in sqlite from strava-offline, it was quite easy to create a local gear tracker that reads rules from YAML and computes component wear. Most of the work was spent polishing this and documenting. :-)
1 comment
[ 3.8 ms ] story [ 10.8 ms ] threadI'm quite a data nerd, so I wanted to track component wear in more detail than Strava allows. Some people on /r/Strava suggested their online web-based gear trackers, but I was always afraid of trusting them with all the data, and also quite reluctant to enter hundreds of components manually. I really prefer to keep this in git rather than in a 3rd party website that can go away. So now that I have activities metadata in sqlite from strava-offline, it was quite easy to create a local gear tracker that reads rules from YAML and computes component wear. Most of the work was spent polishing this and documenting. :-)
[1]: https://github.com/liskin/strava-map-switcher
[2]: https://github.com/liskin/strava-offline