All seems to be good now. In the example you used below, the local time was actually 06:43 on 20/1/16 (I was late getting out of bed that day!) and -hence- UTC was 20:43 on 19/1/2016
Export from run.gps and gps-sport now agree and are correct :)
Can we change one more thing please? When creating a gpx from run.gps the file is give the generic name UNNAMED.GPX. Hence it simply overwrites the last export file. Very confusing. Unless there is some technical reason for this that I am not aware of, please just name it something like GPXYYYYMMDDHHMM.gpx
First step towards correct timestamps in GPS and TCX ...
New releases of Run.GPS (Android, Blackberry, iOS, Windows Phone) will send additional timezone information to GPS-Sport.net. It's already wired on our server and you can recognize such uploads by the timezone added behind the time / date field (see below). (As for now, this is only possible with our beta versions, of course.)
The problem here is that we simply take the local timestamps from the Run.GPS app and store it in the GPS-Sport.net database. Timezone is missing ... Thus, we cannot deliver the correct UTC time from what is stored in our db.
This has to be changed, but it takes some time for all operating systems. The next release of Run.GPS will include the timezone and it will be possible to download GPX and TCX with correct UTC time.
Ummmmm.... just updated to 3.04, recorded a training (ride), uploaded to gps.sport and tried to export the gpx:
Actual Start time: 1509 AEST(UTC +10) = 0509 UTC
Start time shown on Run.gps and gps-sport.net: 1509 AEST [correct]
Start time in GPX exported from Run.gps : <time>2015-06-11T05:09:11.133Z</time> [= 1509 AEST = correct]
Start time in GPX exported from gps-sport.net: <time>2015-06-11T14:09:11.133Z</time> [= 0009 AEST the next day = incorrect]
I imported the gps-sport.net gpx in to Strava and it interpreted the start time as 1720 AEST! Which was the time I uploaded the file. So Strava's algorithm probably suspects there is an error in the gpx (at the time of uploading 1409 UTC was still in the future!), so it just puts a start time of upload time? This is confirmed when exporting the gpx back out of strava which has the start time of: <time>2015-06-11T07:20:10Z</time> = 1720 AEST
So, from here (upside down in Australia :), it looks like the time stamp in the gpx export out of Run.gps is correct, but from gps-sport.net it is incorrect. I can not hypothesise how it arrives at a start time 9 hours ahead of the actual time?
Great, just in time. Just arrived in New Zealand which is +12 +1 summer time =Utc + 13 hours and didn't fancy manually adjusting the gpx files with a jet-lag head :)