Dear all,
What a great addition ClimbPro is to our device. Thank you Garmin.
What a super manual for ClimbPro, thank you aweatherall.
Now I wanted to create a course for a GrandFondo that I have ridden before, making use of my own elevation profile as saved by the Garmin 1030 back in 2018.
With the knowledge of the manual on this forum, I placed the original fit file back on the Garmin and created the course from it. That worked, "but". After loading the course I discovered I had one mountain too many and one mountain with a far to steep climbing percentage. Strange.
I discovered that in the original FIT file, there are 2 mistakes saved. On one occasion the elevation recordings go like this: 1786.4 - 1021.0 - 1786.4 -1786.6 - etc, on another occasion the elevation drops in one second around 800 hm (height meters), returning to normal the next second. I can see this after zooming in on Garmin Connect (you can see the spikes).
I tried to run the original file through the website Garmin.Kiesewetter.nl, but it did not repair and did not convert to CSV. Website stuck. No reply yet on my email to the owner of the site. Bummer.
I loaded the original FIT file in Trainingpeaks and adjusted the values. Piece of cake. Unfortunately from Trainingpeaks you can only download the original FIT, not one with adjusted numbers. Bummer.
I loaded the original FIT file in Golden Cheetah (v 3.5) and adjusted the values. Piece of cake. Hey, from version 3.5 of GC you can export a FIT file, so I did.
Using the GC-adjusted FIT file in my 1030, the 1030 did not recognize a lot of the values. The elevation profile was good though! Conversion to a course did not give errors, but gives 0m of course and 1193 hours (!) of time. Strange and not satisfying. So on we go.
I converted the original FIT file to CSV with the Java Tool, to try to correct the errors in the CSV file and planning to convert the CSV file back to FIT file with the same tool. However, this tool does not recognize a lot of datafields in the FIT file, converting them to "unknown". These unknown fields cannot be converted back to FIT, they first have to be removed. But there are so many that I would lose too much information. Bummer.
New strategy. Convert the GC-repared FIT file to CSV and compare it with the original FIT file also converted to CSV. The GC file is super clean, easy to read, nicely structured. The Garmin file looks like a mess, changing structure (definition of fields) halfway the file several times and is including the same information multiple times.
I have been playing with copying parts of the Garmin FIT file to the GC-repared one and converting the result to FIT. Unfortunately I have not yet found the solution what records will provide the right speed and distance information in the summary after loading the converted FIT file to the 1030 device (hope you can still follow this).
So, until now I have not found a way to just adjust the 2 false height values in a FIT file so that I can use it to create a course with the correct distance, altitude and correct virtual partner speed/time.
Most helpful would be a simple tool that allows us to adjust spikes/values in FIT files so we can make optimal use of the more precise altitude of our past activities in ClimbPro for future use.
Any suggestions on how to get that done will be more than welcome!
