This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Connect messing up elevation on import from 310XT

Former Member
Former Member
I imported a couple of activities after a hiking trip the other day, and noticed that the elevation counts are way off after importing to Connect. When importing the same tracks to other services (Endomondo) they show up more or less correct, however if I export the gpx file from Connect this also shows incorrect data, so there seems to be something wonky with the import feature in Connect. See these activities for examples:

Activity 1:
Garmin: http://connect.garmin.com/modern/activity/546662013
Endomondo: https://www.endomondo.com/workouts/377012664/3533840

Activity 2
Garmin: http://connect.garmin.com/modern/activity/546662188
Endomondo: https://www.endomondo.com/workouts/377012592/3533840

The import was done from the device in both instances, so the source is the same. Elevation correction doesn't seem to make any major difference, it looks like the import feature is messing with the data itself, since the gpx export from Connect contains the same discrepancies compared to the original. Elevation gain/loss is incorrect as well, probably because Connect seems to make its calculations based on the import result rather than using the summary from the device itself. Anyone else have any problems with this kind of behavior?