Data missing, incomplete and GPX export broken

Post a link to one of these problem activities

Hi!

sorry for the late reply, I couldn't get to it earlier. Here are a two samples:

1. hiking today

https://connect.garmin.com/modern/activity/1312937967

Things that don't add up:
- total trip time is 4h 44 minutes -> total time shown in graphs for elevation/speed/pace is 3h 25min (first part is simply missing, if you hover of the elevation graph, all the way to minute 0, you will see the point moving on the track in the main graph, but that point is already way in the track)
- select the "splits" tab below the graphs, the first splits will show no moving time, which is incorrect
- download GPX, you will see that it's wrong (track is from Austria to the equator)
- now select "over distance" instead of over speed, suddenly the elevation graph is complete, but speed/pace graphs still don't show the first part of the track

2. hiking a week ago

https://connect.garmin.com/modern/activity/1302288371

Things that don't add up:
- total time again 4h 46 minutes -> total time shown in graphs is 2h 31min (see the different total time compared to the first hike)
- also all the issues from above

Thanks,
Peter

Hi!

Third issue: GPX exports will provide broken GPX files, that instead of having my bike rides or hikes around the corner, I'm actually hiking from Europe to Africa. This is true for all the GPX exports I tried so far.

It's not going to Africa, it's going to lat=0/lon=0 (which is in the ocean off the west coast of Africa). If you open your GPX file in a text editor and search for <trkpt lat="0" lon="0">
you will find several instances of this error (6 in one of your files that I opened).

I've reported this problem to Garmin, but you should, too, so that they realize it is an issue for many users.
https://support.garmin.com/support/sw/escalateForm

My theory is that when the watch doesn't get a reliable enough location, it records <null> in the lat/lon fields in the FIT file. This is a perfectly acceptable way to handle the missing data. The Garmin Connect Online map knows to ignore these blank data points. If you view the activity in Garmin's Basecamp it will also display the map correctly. However, when you export either a GPX or TCX from Garmin Connect Online it mis-interprets these points and converts the <null> values to 0. This isn't an uncommon error when converting data, but also one that should have been caught during testing.

There is a workaround until they fix the issue with Garmin Connect Online (report the error to them). The GPX export in Basecamp properly handles these data points. It's a couple extra steps to get the FIT file into Basecamp, but it should give you a clean export file.

Ph000, did you pause and restart your walk at an hour in?

I've raised a similar issue recently with the moving time at 0 when the watch has been paused and restarted. See here for my thread:

https://forums.garmin.com/showthread.php?359120-Data-Missing-from-Garmin-Connect-(Moving-Time)

It's not going to Africa, it's going to lat=0/lon=0 (which is in the ocean off the west coast of Africa). If you open your GPX file in a text editor and search for <trkpt lat="0" lon="0">
you will find several instances of this error (6 in one of your files that I opened).

I've reported this problem to Garmin, but you should, too, so that they realize it is an issue for many users.
https://support.garmin.com/support/sw/escalateForm

My theory is that when the watch doesn't get a reliable enough location, it records <null> in the lat/lon fields in the FIT file. This is a perfectly acceptable way to handle the missing data. The Garmin Connect Online map knows to ignore these blank data points. If you view the activity in Garmin's Basecamp it will also display the map correctly. However, when you export either a GPX or TCX from Garmin Connect Online it mis-interprets these points and converts the <null> values to 0. This isn't an uncommon error when converting data, but also one that should have been caught during testing.

There is a workaround until they fix the issue with Garmin Connect Online (report the error to them). The GPX export in Basecamp properly handles these data points. It's a couple extra steps to get the FIT file into Basecamp, but it should give you a clean export file.

Thanks, I did that. I think your explanation sounds reasonable, they just misinterpret the null with 0. This still doesn't explain the missing data in the track I guess.

Hi ph000,

I posted to this thread around 13 hours ago and apparently it still hasn't be approved by a moderator so here goes again.

Did you pause your watch on your walk after around an hour?

A couple of us have raised an issue and done our own analysis on this issue and noticed that once pause is pressed, and resumed, and the data is uploaded to Connect it seems to disregard what happened before the pause/restart and the Moving Time is put to 0.

See my thread here to see if it's the same issue:

https://forums.garmin.com/showthread.php?359120-Data-Missing-from-Garmin-Connect-(Moving-Time)

Hi ph000,

I posted to this thread around 13 hours ago and apparently it still hasn't be approved by a moderator so here goes again.

Did you pause your watch on your walk after around an hour?

A couple of us have raised an issue and done our own analysis on this issue and noticed that once pause is pressed, and resumed, and the data is uploaded to Connect it seems to disregard what happened before the pause/restart and the Moving Time is put to 0.

See my thread here to see if it's the same issue:

https://forums.garmin.com/showthread.php?359120-Data-Missing-from-Garmin-Connect-(Moving-Time)

Hi!

yes, I did definitely pause the track a couple of times, sometimes accidentally and also for lunch. It could definitely be, that the interruption starts at the first pause. The later pauses seem to be handled correctly in the graphs.

-Peter