Dodgy elevation on Spartan Sport WHR
-
@RiphRaph
Yep, in fact it is a (pre) lock screen -
@sartoric Meaning what, exactly?
-
@RiphRaph
That you can lock the screen from that view
-
@sartoric By doing what once youāre in that view? The manual doesnāt seem to mention any of this in detail!
-
@RiphRaph
Ehmā¦ Donāt you have a Spartan?In that view there is the option ālockā
-
@TELE-HO just got, for the first time, your described effect! Today I did a 13k walk and because of the storm that is over western europe I wore a puffy jacket, and my watch was under the jacket. Got a very good GPS+Galileo track, but elevation gain of over 230 meters, and in Amsterdam that is quite unrealistic. Probably a factor 10 off. And very spiky like you describe.
Watch: Suunto Vertical Ti
Blog: isazi's home
-
@isazi
there are some activities for me where wrist motion and watch position cause spiky and wrong alti recordingā¦ for me as a design engineer the sensor is not at the best possible location. design should follow function.
since I donāt use OHR I generally wear my S9B looser around the wrist, this helps to avoid spikes. a longsleeve that goes underneath the watch body helps, tooā¦ but thatās nothing for summer month or gym workoutsā¦I hope Suunto considers this for a potential S9B successor
and thanks for your confirmation, for me it proofs that I am not dreaming or hunting ghosts
-
@RiphRaph said in Elevation Gain:
This post may answer your question:
https://forum.suunto.com/topic/3886/dodgy-elevation-on-spartan-sport-whr/5
If you have a non-baro model and your route is only mildly hilly, that 7m threshold may mean your elevation data bears little resemblance to reality.
This seems to be the best explanation.
Nevertheless it is rather disappointing, that the elevation is not calculated (at least estmated) in the app, because it seems that the watch - although not counting elevation less than 7m - is nevertheless registering the elevation: in the app the āelevation-graphā is displayed as correct as it is possible with GPS-only.
I would like to have a ācalculatedā elevation (marked as this value), based on the elevation shown in the graph, if possible and available supported by the elevation according to the map / track. -
Reviving this thread because I just noticed that my Stryd gives me fairly accurate elevation info. For todayās flattish 5.5km loop, the Spartan claimed all of 7m of elevation. Clicking on ācorrect elevationā in Strava yielded 20m, while PowerCenter claims a total of 30m of ascent.
The Suunto algorithm is waaaay off the mark here. The correct figure is somewhere between Stravaās and Strydās claims; I suspect that Stryd comes closest to nailing it. It would be really nice if the watch could take not only pace and distance from Stryd, but also elevation as well, seeing that the footpod is so much more accurate!
-
@RiphRaph The Stryd has a barometer, that is why it is so much better. Without the barometer the watch will simply not be as accurate. I think it would be difficult to get elevation data from Stryd as the unit does not likely broadcast elevation as it does power, distance, pace and cadence.
-
@Brad_Olwin Iāve just learned on the Stryd forum that Stryd DOES broadcast elevation data, so it would be possible for Suunto to use it.
I think this would be a great idea, especially (but not exclusively) in the case of non-baro watches.
Formerly Spartan Sport WHR, happy Coros Vertix user since Sept. 2020
-
@RiphRaph but as with every other technology, nothing is perfect. I just checked a weighted climb I did two weeks ago with Stryd and my S9 baro: the watch says ~320 meters of elevation, Runalyze says ~420 meters of elevation (they apply a different threshold and reprocess the FIT file sent by Suunto), Stryd says 230 meters of elevation. Now which one is the right one? I have no idea
-
@isazi Fair enough. But I was mostly thinking about non-baro watches. Any barometer would yield more satisfactory data than an algorithm that thinks seven equals zero.
-
@RiphRaph I think that the algorithm doesnāt think that 7 equals zero, Iām quite convinced that it thinks: Iāve arrived at 7 during certain period of time then I start to count (and I guess it includes the 7 m).
-
@cosmecosta said in Dodgy elevation on Spartan Sport WHR:
@RiphRaph I think that the algorithm doesnāt think that 7 equals zero, Iām quite convinced that it thinks: Iāve arrived at 7 during certain period of time then I start to count (and I guess it includes the 7 m).
This discussion have already been placed somewhere here by a former user, and great discussions about ascent algo with @Dimitrios-Kanellopoulos.
I also think the last S9 FWs have changed the way ascent is cumulated, but no so sure to remember correctly. -
@cosmecosta Iām not sure. One of my fairly flat 5k loops registers 30m of total ascent for Stryd but 7m (and on some memorable occasions, zero m) on my non-baro Spartan, so it doesnāt look to me as though those initial 7m are being considered.
As has been noted before, this isnāt exactly a mountain trail; the undulations are pretty minimal. Still make a difference to effort/power though, which is why I find them of some interest.
Formerly Spartan Sport WHR, happy Coros Vertix user since Sept. 2020
-
@Mff73 said in Dodgy elevation on Spartan Sport WHR:
@cosmecosta said in Dodgy elevation on Spartan Sport WHR:
@RiphRaph I think that the algorithm doesnāt think that 7 equals zero, Iām quite convinced that it thinks: Iāve arrived at 7 during certain period of time then I start to count (and I guess it includes the 7 m).
This discussion have already been placed somewhere here by a former user, and great discussions about ascent algo with @Dimitrios-Kanellopoulos.
I also think the last S9 FWs have changed the way ascent is cumulated, but no so sure to remember correctly.Even if it has been changed, it still does not work satisfactorily on a Non-Baro 9. After a run with good GPS-reception on a not too flat course I quite often receive the 0/7, 7/7, 0/21 etc numbers, while the - realistic - graph in the app shows a very different picture. It seems elevation is tracked rather nicely and not too badly, but is not used at all in SA (or even MC).
In my opinion not the best approach at all - I would really like to see the acquired data (altitude) used in a better way. -
@RiphRaph That is cool, I did not realize Stryd would broadcast that. Would be useful for non-baro watches.
-
@RiphRaph Had exactly the same problem with my spartan trainer wrist, some of my usual runs with 90m turned into 0m now! what is happening?
-
@RiphRaph I agree. my 273m turned into 100m since last update. what can i do?
