I think there are two problems which result in a similar outcome - namely a timestamp that goes backwards in time. One is the FIT file storing timestamps before and after a GPS sync and the other is the Isaac merge which has problems with TCX files as well.racerfern wrote:IMO even though there may be a problem in merging some files, I think the root cause is the FIT file. If you convert the FIT to a TCX the issue goes away because the converting software fixes the error in the FIT file. AFA not finding other rides on Strava it may be that Strava has to make some adjustments since it appears Garmin has no interest in fixing the issue.
I've got an Edge 705 which only stores TCX files so I'll see if I can mimic the late GPS synch and see what it produces.
Revert doesn't work on the GPS data or the timestamps. BTW - another bug in the merge is that even if you do not choose Garmin timestamps it uses them anyway. If it used the Newton timestamps there's a good chance the backward timestamps would disappear.rstrom wrote:KenS - was that my file that you're referring to? If so, isn't it possible to revert to the Original file download? From the Analyze menu ... Revert to Original Download.
I don't know if that will give you what you're looking for or not, just a thought / suggestion.
I've got a pretty good idea why the merge has problems which you can often see on any"before merge" chart. The Garmin plot is invariably longer than the Newton plot by the amount of stoppage time. So the chart is showing the Newton data based on ride time while the Garmin data is based on actual time. If that is the same data that is being used to synch the files then it's little wonder Isaac has problems synching when it reaches one of the stops.