[GregBoys]

Hi all,

I wonder if anyone has noticed the same. Since the recent update to MovesCount, and it's automatic intergration with Strava I'm seeing incorrect altitude readings. Instead of a nice smooth graph showing the elevation of my ride in Strava, I see a lot of spikes.

I get the same issue if I export the ride (or run) from MovesCount as a TCX file and import it to Endomondo. It reports a massive ascent & descent (3415m for latest ride), but a max altitude of 98m. However if I export a GPX file I get a proper elevation graph (I prefer to use tcx as it contains cadence data)
I'm more concerned about the Strave data though as it is throwing out the wattage calculations for climbs, segments etc.

My watch is an Ambit 2S on 2.0.9 firmware, and I running v1.1.53 of Moveslink on an XP PC (I know, I know)

 

[SiRoB1]

Hi GregBoys,

first Suunto TCX or FIT exported files don't contain all elevation information.
When you import these files to Strava, you need to wait a bit to let Strava uses it's own elevation correction.

When you check your move on strava you may notice that the elevation is totally wrong.
There is a note under this wrong elevation.

Currently there is some heavy load to Strava, maybe due to new Suunto link connection to Strava.
And it's why you need to wait more.
Don't remove your activity from Strava because you think it's a mistake, let Strava servers the time to complete the process.

 

[morey000]

I contacted Suunto about this. They are aware of the problem and said that a fix for the strava altitude issue would be released shortly.

 

[GregBoys]

For anyone following this I see from Movescount facebook feed there has ben a fix. I'venot tested it personally yet.

The recent Movescount update introduced the latest addition to our partner applications, Salomon Citytrail - www.movescount.com/connect/citytrail

Otherwise, the update consisted of bug fixes and usability improvements, such as:
- New: Move without gps info can now be exported as a .fit file
- Fixed issue with map being grey and graphs missing after lap
- Fixed issue with Quest/t6 Move graph not drawn after pause
- Fixed issue with altitude values in .tcx file export & when transferred to Strava
- Fixed multiple language / translation corrections.

 

[SiRoB1]

Fixed issue with altitude values in .tcx file export

TCX files seem to contain all elevation information now.
Thus, strava servers will no longer be overloaded by Suunto users.

edit: Anyway i'm not sure it's the proper way for ambit without altimeter.
I'm pretty sure you should get better accuracy by using corrected strava elevation.

 

[SiRoB1]

Just tested by using FIT files and they still force strava server to correct elevation.