Altitude bug in one fit file export ?

[Mff73]

Hi,
Yesterday’s skitouring activity, perfect data in SA (at least SA doesn’t show anything wrong).
But in external tools, and in QS, my altitude is … how to to say

I uploaded Raw data file in QS to compare, and :

It looks like :
1- Fit file altitude hesitates between raw data altitude and GPS one
2- raw data are nice : registered altitude AND GPS altitude
3- registered altitude is a bit far from GPS altitude, so i imagine fusedalti didn’t work (but i am used to)

for example on one point :

And it is well in the fit file

Conclusion :
14000m ascent in other tools

[Dimitrios Kanellopoulos]

@mff73 link or workout id

[Mff73]

@dimitrios-kanellopoulos said in Altitude bug in one fit file export ?:

@mff73 link or workout id

I was expecting this question Link in pm

[Gábor Tóth]

@mff73

Hi guys. In the last two activities I had a similar issue. Same thing happened with the altitude data as it was described here. First i thought it was a clogged barometer holes, but it seems like its not a “local” issue. The data seems to be OK in the SA - but in partner services are displaying totally wrong altitude data.

[Dimitrios Kanellopoulos]

Known under investigation and fix . HOld on

[Dimitrios Kanellopoulos]

@gábor-tóth should be fixed now

[Mff73]

@dimitrios-kanellopoulos said in Altitude bug in one fit file export ?:

@gábor-tóth should be fixed now

for me too ?
It is ok now in Runalyze after reimport
Before

After

Downloaded fit from QS, and reimported in QS, and graphs are smooth like expected.

Thanks man and to support team.