The battery on my Edge 820 died roughly 2 miles from home, at the end of 110M ride. Not a problem - I have loads of activities I can extract the final part of the ride from and append to the activity, to create an accurate(ish) record of the ride. (I wouldn't normally be so anal about this, but it was the first time I have ridden over 100M in one day...). One three hour pause in middle of ride.
Two files exported to gpx from Connect (web). File1 the gpx of the actual ride, File2 my ride from which I will pinch the "missing" data. Using Notepad++ I adjusted several fields in File2 so would match File1 (time / date / temp). In File1 renamed the "track" name, and then cut / paste the data from File2. Saved File1 as new File3
Uploaded File3 to Connect (which then syncs File3 to Strava) All works, and the mileage / track etc are all good except moving / elapsed time display. That is, for the original activity uploaded from actual device to Connect (the original fit file) (using round numbers):
Time 9:00:00 (I assume this is the time the 820 is recording an activity, regardless of whether you are moving - waiting traffic lights, junctions, having a chat and forget to pause activity etc)
Moving Time 8:00:00 (time the bike is actually moving and activity is recording)
Elapsed Time 12:00:00 (essentially the sum time between when I first started recording the activity and the time when I saved the ride - total moving time + total non-moving time + total "device standby / pause" time
File3 in Connect displays [Time] and [Elapsed Time] as identical - that is, it appears to not be able to recognise the big pause in the middle when it is getting it's data from a gpx file.
Strava does display it's version of [Moving Time] & [Elapsed Time] roughly the same whether using the original data, or the File3 amended gpx.
Question:
Is there something in the original fit file that allows Connect to recognise the "extended pause / break" in the middle of the ride?
Is there a way I can amend the [Time] value in Connect, so it doesn't show the same as [Elapsed Time] ? (8 or 9 hours shown on the activity page is far more flattering to my ego than over 12hrs! :-) )
Thanks for any insight or suggestions.