During an exercise, Garmin allows you to pause recording so that your split times and pace are not affected. How are these paused periods represented in the TCX format? I've looked through the TCX schema, but did not find an obvious answer.
In the TCX format, how is a trackpoint marked as paused?
3.5k views Asked by Well Actually AtThere are 4 answers
The activity in a TCX file is divided into laps. Each lap contains one or more Tracks which contain Trackpoints which are the individual records of position, heart rate, and so on. If you pause and restart the watch, the pause closes the current track, and the restart opens a new Track. So, for instance, if you pause twice in the first mile, using auto lap at each mile, the first Lap will contains three Tracks. Analysis software should use this structure to work out that the watch paused after the last Trackpoints in each Track and restarted at the first Trackpoint in the next Track.
I couldn't find any documentation of this either; it's based on inspection of Garmin data when I was working on the same problem when I needed to convert Timex .pwx files into TCX to upload to a site that didn't properly support pwx.
I don't know if this helps, but I have a FitBit watch and I accidentally pressed the pause in the middle of one of my rides. I wanted to correct it, I never found any documentation on how to fix it. So, after some random attempts to fix it by uploading and downloading the file in different formats I found something. The original file when uploaded to Ride with GPS had many trackpoints with:
<DistanceMeters>0.0</DistanceMeters>
The total distance reported on Ride with GPS was 7789.23 When I downloaded the file from Ride with GPS again I realized that the trackpoins which had distance marked as 0.0 would have then 7789.23 as
<DistanceMeters>7789.23</DistanceMeters>
So I got my original FitBit file and removed all 0.0 DistanceMeters Then I uploaded again and it fixed my distance to the correct final distance should have had. Also, I saw that my original FitBit file had the Lap distance as 7789.23, but I did not have to fix it on the lap itself. So the answer is on the calculated distance and speeds which may be skewed when hardcoded by the tracker.
Below an excerpt from a TCX file where I pressed "Stop" and later "Start" again... perhaps this helps.