Solved issues
- Calories burned information was wrong for (non-swimming) activities with more than 1 segment/lap (e.g. when activity was paused or GPS loss occurred during activity). For each subsequent segment/lap, the calories of all preceding segments were added again which caused a too high total calories burned value in Strava. Closes #5.
- Segment/Lap distance information was wrong for (non-swimming) activities with more than 1 segment/lap.(e.g. when activity was paused or GPS loss occurred during activity). For each subsequent segment/lap, the distances of all preceding segments were added again which caused a wrong value in the Lap overview in Strava. Closes #6.
Known Limitations
- Calories burned information is not available for swimming activities (need real-life data to code/test).