Looks like the GPS date glitch is stopping the miles counting against this year's mileage total
- I'm pretty sure it said 1390+ yesterday, so should be 1470+ today.
I see that other tracks were from an edge 1000, but this one is tagged as from a 510. Is it a backup device? (speculation: perhaps last used on that erroneous date in Sep? leading to the "current" track having an erroneous start time/date?? which would be borne out by the bizarre elapsed time).
Given the 24hr upload requirement for each days track, is there someone on Steve's team dealing with stuff like this for him while he rides - e.g. checking what the discrepancy in the track is and notifying UMCA etc.?
If it's something as simple as a the <time> tag in a single trackpoint wrong, (or even just a wrong <time> field in the metadata section?) then the track .gpx could easily be fixed,
but that would, I imagine, need to be done with the knowledge and agreement of the UMCA.
Otherwise, substituting the track from his second GPS device might be easier, but only if that track data is available somewhere while he is riding.