Hi,
I read my Garmin Forerunner 305 by using GPSbabel. Very convenient. Especially when I read multiple sportswatches after a race, from different people, and I don't want to create a new account for each of them.
However, Routegadget does not like the tcx output of GPSbabel. The reason is that the data file does not contain the correct start-time in the Leg header and does not have an unique ID. Yet, it could be interpreted by Routegadget if Routegadget would just look at the date/time of the first sample in that Leg. The Lag ID/date is used in the dialog where you have to select which Leg (track section) you want to use in Routegadget.
An other option would be to just concatenate all Legs (and use the cut option in Routegadget) when they can not be identified by their header.
But ignoring the headers sounds simpler to implement.

Would this be an idea for a next release of Routegadget? (I am also trying to get GPSbabel fixed in this respect; but redundent robustness is preferred in my opinion).