Editing a Garmin .tcx file

[yello]

Today's ride log got spiked. Apparently, my max speed was over 2500kph. I want to edit the .tcx file and remove the offending data. The file is xml so it should be straight forward enough. That is, if I knew how the Garmin recorded the speed. A speed entry tag looks like this...

<ns3:TPX>
<ns3:Speed>6.439000129699708</ns3:Speed>
</ns3:TPX>

That speed isn't kph, not even mph. Anyone any ideas? I can't find an XML schema on the Garmin site. It seems to be something new too since it seems to be the first .tcx file I've had with such a format, previously there was no such tag and so I presume it calculated it.... hmmm, thinks... maybe I could strip all these ns3 tags and see what happens when I import it....

Interestingly, ridewithgps filters that crud data out, or ignores it, and reports the correct maximum speed BUT Garmin Connect doesn't.

 

[frank9755]

I used a program called TCX converter once to edit a TCX file. I needed to cut a chunk off the trace (as I forgot to switch the Garmin off before I put my bike in the car and drove home!) so not quite the same need as you, but I remember that:
It gave loads of individual data points which you could edit
It was a lot more complicated and fiddly than I had expected it to be

Might be worth a try if no-one has any better ideas.

 

[gaz]

Depends how your data is set to record, but it is either meters or feet traveled in a second.

 

[amaferanga]

The ns3 tag is added when a ride is exported from Garmin Connect I think. If you look at the .tcx file that's stored on your computer it shouldn't have the ns3 tag.

 

[yello]

It's probably set to meters per second then as everything else is metric.

You're right amafarenga, I was looking at the wrong tcx file, the one exported from Connect. The one exported from GTC contains no speed data - so it's going to be a bit more tricky to edit on the spike.

 

[yello]

Got it sussed now. The max speed is a tag all of it's own at the head of the file, and it's in meters per second.

I don't reckon the logging spiked as such. We passed through a number of tunnels today (one of 1.7km) where the Edge lost reception. I reckon that may have messed up the max speed calc somehow.

 

[zacklaws]

Got it sussed now. The max speed is a tag all of it's own at the head of the file, and it's in meters per second.

I don't reckon the logging spiked as such. We passed through a number of tunnels today (one of 1.7km) where the Edge lost reception. I reckon that may have messed up the max speed calc somehow.

There's three methods I use:-

The first is to use XML Notepad 2007, from Microsoft. Just open the XML file in it, search for the actual speed you was doing and edit it out to something more reasonable and save. There may even be a newer version out.

The second is to import the file, TCX, into Sportstracks and just search for the bit where it is iffy and make a split at that point just before it goes iffy, then in the second part of the split once again cut out the iffy part, and then rejoin the two parts.

The third, import TCX into Golden Cheetah, go into the editor, search for the iffy parts and edit them out.

And I think you can also use TCX converter as mentioned but I have never used it to edit a file before so do not know how

Whichever method you use though make sure you have a backup in case it goes wrong

Just had an experiment with TCX converter and it is a simple job I think.