Now that I have the initial import working, i'll add a check against ES to prevent sending a duplicate activity to ES during imports. Including some that were initially imported from run keeper to garmin, resulting in very odd formatting. Imported all 377 activities from my garmin account going back 2.5 years. The current version of the parser is here. Generate json logging/send to Logstash 'ready to go' for ES/Kibana.Convert fields into usable formats for Kibana graphing.Read conf file indicating format of csv/important fields for each activity type in the csv.I ended up writing a python parser to do the following: The biggest issue were pace/speed fields varying. Unfortunately Garmin is not consistent with it's data formats in events. Initially I tried to just use a file input on logstash with the csv filter. The simplest method for data I found was to manually export(20 events at a time.) from garmin connect. Unfortunately Garmin charges(!) to use their API. What is my cadence/pace on only >20km bike rides? Control the date range - Garmin has week, month, 6 month, year fixed views, and fixed buckets in said views. At 6 months or a year, you only get monthly counts. The quality of reports on garmin connect is disappointing to say the least.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |