-
OK, I know the SSWHR doesn’t have an onboard barometer and gets its elevation figures from GPS. But the figures still look highly dodgy. Exhibit A: for today’s run, the highest point was allegedly 545m and the lowest point was 510m. This seems plausible given the topography of the route, but at the same time the watch claims that the route had 7 m of ascent and 7 m of descent, which is where things stop making sense.
What’s the deal there? Do I have a broken watch or is the non-baro Spartan Sport just generally useless at elevation?
For whatever it may or may not be worth, Strava corrects the elevation to 49m. Which I suspect is still too low given how much the route undulates, but at least it isn’t patently absurd.
-
@RiphRaph
depending how long the distance is, a difference of 35m is almost flat. but you’re right, when the watch records lowest and highest and the ascent is only 20% of the difference it is strange.
we have discussed this topic in depth couple of months ago in other non-baro watches threads.
my very basic comment is: if alti counts there is no way around a baro watch.
but my wife runs with an A3R also without baro but she has very accurate and reasonable ascent values… but also the topography where we live has higher and lower alti than your example route -
@TELE-HO Sorry, I should have said. It’s a 10.5 km loop. Most of it is either slightly uphill or slightly downhill; there’s effectively no truly flat ground anywhere in these parts. So 7 m of ascent is just ludicrous and the ascent time is claimed as two minutes and change, which is even more ludicrous as pretty much half the route is on an upward grade!
I came to Suunto via Tomtom and the Runner 3 (which AFAIK didn’t have a barometer either) consistently reported the ascent of that route as between 84 and 87m. I guess the Spartan is just broken in this respect.
-
@RiphRaph please search the forum, as there is a long discussion on this issue. Short version, the non baro watches have higher thresholds for computing elevation/descent than baro watches.
Watch: Suunto Vertical Ti
Blog: isazi's home
-
@isazi
e. g. this contribution from our friend, the former user…"The actual algorithm is far more complex than that. The barometer resolution is 1m or probably even higher on modern Suunto watches, but you can try going up and down 2-3 meters and your watch will count zero total ascent even if you repeat that 100 times.
There’s a threshold, which is 3 meters for baro watches and 7 meters for watches without baro, and the total ascent / descent increment in chunks once the altitude change exceeds that threshold.
As an easy experiment you can customize a sport mode to have altitude and total ascent together on the same screen and just watch the two fields together. You’ll see that the total ascent lags behind altitude changes and in many cases it may not register the last few meters or a climb as you crest over a hill even if those few meters exceed the threshold."
https://forum.suunto.com/topic/3296/bug-of-positive-elevation-alti/56
-
@TELE-HO Thanks so much for linking to this. So I conclude that my watch is behaving “correctly”, that it’s the 7m threshold that’s throwing off my elevation figures, and that there’s nothing that can be done about it except switch to a different watch.
Rather disappointing that the Tomtom could do it so much more accurately for about a third of the price, but there it is. One step closer to becoming a Former User myself.
Formerly Spartan Sport WHR, happy Coros Vertix user since Sept. 2020
-
@RiphRaph
I would observe the different trails you’re running and compare the total ascent to what you expect or measure in an external tool. Maybe the offset isn’t that big on other trails and you can happily live with what you have instead of investing in another watch.
It is difficult to figure out what the different watches do in the background, even within one watch maker. I think also Ambit3R and Spartan Sport have different ways to calculate total ascent.
But yes, as said, if you value a good precision of total ascent I would consider upgrading to a baro watch.Side comment: A3PS and S9B, both baro watches do record different total ascents on rolling terrain… I did not compare recently as I gave my A3PS to a good friend… but back when I did comparison the S9B did calculate a littlebit too much.
-
@RiphRaph if your watch didn’t have that filter it would produce unrealistic ascent’s.
Could I have a comparison of your prev tomrom with the Spartan to understand ?
-
@RiphRaph different watches have different algorithms, and you’ll see people complain a lot about elevation on other vendor’s forums too.
-
@TELE-HO The offset is about as big on other routes as well. Just checked my other regular loop and the Suunto claims about 25% of the ascent that the Tomtom reported. I guess I will be looking out for a baro watch, because this is just nuts.
-
@Dimitrios-Kanellopoulos It produces unrealistic ascents with the filter as well. QED.
Do you mean you want to see actual gpx files? I can provide those, but not via links in a post here as I don’t want to disclose location info on a public forum. Can I send them to you privately on this forum? I’m not yet very conversant with how things work around here.
-
@RiphRaph said in Dodgy elevation on Spartan Sport WHR:
Send me a chat message pleaseYou can upload them to dropbox / drive and pass me the link
-
@Dimitrios-Kanellopoulos OK, just did that.
-
roger that
-
@Dimitrios-Kanellopoulos even with baro it looks weird when I see my data in QS.
Elevation gain/loss is over 600 meters:
But the watch says:
Is Ascent/Descent same here as total elevation gain/loss. My understanding is that the Ascent/Descent are totals from whole activity:
The altitude uses baro only here (no GPS, it’s indoor, it’s always either going up or down without GPS).
@RiphRaph I think my issue may be related/similar but if not then sorry, I didn’t mean to hijack your thread
-
@jsr184 QS uses the minimal 1m calculation for charts. You can edit this on settings.
Your hand moves more than 1m FYI its logical. That is the case why all companies use filters. See my reply above
Community Manager / Admin @Suunto
Creator of Quantified-Self.io
youtube.com/c/dimitrioskanellopoulos
https://instagram.com/dimitrioskanellopoulos
https://www.strava.com/athletes/7586105 -
@Dimitrios-Kanellopoulos “the diff is so small”?
On the 8 km route, Tomtom reports 68 m of ascent and the Spartan reports 22.
On the 10 km route, Tomtom reports 86 m and Spartan reports 14.In what world is this a “small” difference?
Formerly Spartan Sport WHR, happy Coros Vertix user since Sept. 2020
-
@RiphRaph I am sorry. I read 44 vs 52 as seen in the pics.
-
@Dimitrios-Kanellopoulos is 1m means meter or minute?
Don’t get angry please, but I don’t think I understood what you’ve been trying to say The thing is that if I do a climb of 9-10 meters up and then I’m being belayed down it’s usually 2-3 minutes of staying pretty much in the same location in 2D floor space. Hence, what QS shows looks more real. I don’t believe that my total ascent registered by Spartan was just little over 100m while I spent in the climbing centre over 8 hours doing just that - climbing (average route 7-10m high). Is it possible that my higher climbs are filtered by Suunto because it assumes no one suddenly can shot up in the air so far in such a small area? 622m vs 111m is even greater difference. -
@Dimitrios-Kanellopoulos
all the tiny spikes in @jsr184 's recording could also be sealed sensor holes and pumping effect…living sideways
