Wrong ascent value 0m
-
My Spartan Sport WHR always shows 0m ascent in the new Suunto app. In the Movescount it shows a correct value.
-
@igvol do you mean for activities imported from MC, or for new activities synchronized with SA?
-
@isazi said in Wrong ascent value 0m:
@igvol do you mean for activities imported from MC, or for new activities synchronized with SA?
@igvol
Or do you sync your watch with Movescount and then activities from MC to Suunto App with Syncmytracks? -
Same happens to me. Since a couple of days back, any move or route in my library in Movescount shows 0 ascent value. If i create a new route, it shows distance but not altitude. Even in my previous moves, i can see the ascent and distance next to the name of the activity, but when I click on in to see move on the map, no elevation profile is shown. It looks like the maps in movescount have no information regarding elevation anymore. Any of the maps (road, heat, mapbox, google,…)
-
@miamigojack
Route with no elevation in MC is known issue, please search in this forum (mapbox issue linked).
Moves with no ascent is “new” if really you are talking about activities synced from a Suunto watch to Movescount.
I checked on my side and Altitude graphs are still there in MC for Moves (and not routes). -
How do you import the workout in Suunto app? using a third party app?
-
This happens when I sync new workouts using the new Suunto App. They are not imported for the MC. The ascent always shows 0m.
-
@igvol said in Wrong ascent value 0m:
This happens when I sync new workouts using the new Suunto App. They are not imported for the MC. The ascent always shows 0m.
-
@igvol Are you syncing directly from the watch to the app? Which OS are you using, Android or iOS?
-
Yes, sync is directly from the watch to the app. I’m using the iOS.
-
I set the GPS accuracy to Best and now the ascent shows a non-zero values. In any case, this value seems to be inaccurate because the watch doesn’t have a barometer. I’m using Strava’s elevation correction feature to get the right one.
-
@igvol said in Wrong ascent value 0m:
I set the GPS accuracy to Best and now the ascent shows a non-zero values. In any case, this value seems to be inaccurate because the watch doesn’t have a barometer. I’m using Strava’s elevation correction feature to get the right one.
Yeah, only in GPS best, altitude is recorded using GPS information.
Don’t know why no one of the experts here suggested this first
And yes, altitude from GPS is not super accurate and depends on the satellite reception.
That’s why there are devices with a barometric sensor. -
@Egika I’m unsure why Suunto makes the lower fidelity gps readings (which are great for extending battery life) so useless by not allowing ascent to be calculated or correction anywhere within the Suunto ecosystem especially when the elevation readings are pretty reasonable with those less frequent pings. The only way to fix after the fact is in Strava which is a little manual and frustrating when Suunto could fix on their end. Even really low price Garmin watches with only GPS altitude always have a good ascent value calculated as compared to the 7m algorithm Suunto uses so I don’t really buy the whole ‘you need a barometer to get any good data’ theory because I used to get really good data from a $150 Garmin but now when I use my SSWHR in Good or OK GPS I can never get an ascent value above 0 in Suunto App.
-
@Matthew-Pierce I am sure if it worked reasonably well, Suunto would implement it.
OK GPS setting means the GPS chip that does the calculations is powered off most of the time and only enabled briefly. During this short time the error is bigger (and the vertical error is even bigger). -
It looks like a regression in the new Suunto app. Same watch with GPS set to Good did show non-zero ascent in the old Movescount app.
-
@igvol Perhaps MC calculated the vertical ascent data, the watch does not when set to anything other than best GPS. The 7m hysteresis is a trade off with best GSP for getting the most accurate altitude data for relatively flat vs. mountainous terrain. If SA recalculated the altitude data then you would be able to get non 0 ascent. TrainingPeaks, Strava and Runalyze all can do this. Once SA is opened up for import a workaround would be to cycle through a third party. You could suggest this as a feature.
-
@Egika I get your point and yes that makes sense, I’m just not sure if they took it far enough to solve the problem. Making sure erroneous data isn’t in the users experience is a worthwhile effort, however giving them reasonable proxies (something is better than nothing) might be more worthwhile.
Moreover, the only time that you would use these battery modes would presumably be longer efforts where less GPS accuracy doesn’t matter as much, as in all day hikes at a slow rate …but those activities if in mountains would be scenarios in which having a little error that accumulates over hours for ascent values would be preferred to 0m elevation gain reported which over a day is likely to be more ‘wrong’ than the error-ridden ascent value. In either case one can correct these in Strava or Runalyze or other 3rd party sites after the fact so I’m not concerned with the after the fact, just the day-of utility of the measure. There could also be something to 5 second or 10 second full power rate versus 1 sec low power rate if power setting is more impactful to vertical accuracy than rate of connection, although having not had a watch that had those I don’t know if those had any better (if more coarse) ascent values possible.
Those are just my thoughts on it, I bought the watch as a running/hiking watch so I guess I should have done more research before purchase when the longer duration battery settings come with such heavy caveats…