start/end time errors from TCX file (via Nike Run Club?)

[fatguypat]

Hi All,

I've been having difficulty repairing quite a few TCX files I received via a data request from Nike Run Club, for a few activities, the start/end time is incorrect- as in the end time lists a timepoint that is earlier than the start time, here is an example.

Im not sure how to go about fixing this. Some things I know for certain about the example running activity pictured in the photo is that 1. The running activity took place in southern California on 03/05/2015, It is listed in my Strava and Nike Run Club activity, but does not contain any GPS data, but on the repair tool, it shows 41 points and the correct start and end time/date but the map is in London?

Any help on how to fix this file would be greatly appreciated. thank you so much

[fulmar2]

Hey fatguypat -

Generally, TCX files are just XML, so they don’t really need “repair” in the traditional sense. From your screenshot, I can see that the latitude and longitude values are 0,0. By default, Leaflet maps will display London whenever they encounter either:

• an indoor activity with no GPS data, or
• a 0,0 lat/lon coordinate.

That explains why your activity is showing up there.

Your file does contain 41 points, but most of them look like empty timestamps with only a cumulative lap and distance included. That’s why you’re seeing very little usable information.

If you’d like, you can upload the original TCX files here on the forum. With the raw files, I’ll be able to take a closer look and see whether there’s any additional data we can extract or reconstruct.

[fatguypat]

thank you- appreciate you taking a look, ive uploaded the file as part of this reply- also more about the running activity in the og post. I can recall it was approximately a 5Mile outdoor run. It was not done on a treadmill/indoor, and I believe I used the Nike run club app on my iPhone to record the activity- if that info helps.

[fulmar2]

OK, bad news. It appears that the Nike Run Club uses non-standard TCX formatting. GOTOES was able to retrieve all of the data.. but there just isn't much there; most of it is "NikeFuel". Note that there are not GPS coordinates in the original file - that is why there is no map. Also, the reason you're getting the stop time error on GOTOES is because Nike is writing the TCX file in the wrong order.

If you really want a map, you can do that, but without any sort of position or speed data, you're really just going to have to fabricate it all.

Also, just to clarify, I understand that your original activity was outdoors... however if the TCX file does not contain latitude / longitude, it will be perceived as an indoor workout.

The only other suggestion I have for you is to see if there is another export method you can try... if you can get files that contain more data (and are properly formatted), this should work.

[fatguypat]

I appreciate you taking a look at it. I'm not sure what I was supposed to do with "NikeFuel" data, let alone what IT is anyhow. I have quite a few runs in the 2015-2016 timeframe that have this issue (only pace, distance, total time captured- no GPS). I think rather than make an ill attempt to "complete" the data activity with fabricating map data I might just leave as-is.

thanks again