Data quality
-
@sartoric good catch
-
@sartoric however I dont
-
@sartoric is it with OHR?
-
yep.
Just done a new move test and it looks fine
-
@sartoric said in Data quality:
-
@sartoric any tip to help why this happened on old moves?
-
@sartoric I could reproduce it
-
I really don’t know …
for sure 1sec has been added to the HRZ time , even if HR hasn’t been modified (or doesn’t looks modified).
In fact the graph just looks shifted and messed upthis is the move : http://www.movescount.com/it/moves/move242084616
-
More than 100% !
-
@Dimitrios-Kanellopoulos
Just noticed that in my move the watch Z1 has been removed and Z1 in graph is in fact Z2 from watchHas some correction been applied to the zones ?
-
@sartoric I suppose
-
Just checked another one with time in Z5
-
@sartoric clear its a regression issue fixed asap (expect a soonish beta)
-
@Dimitrios-Kanellopoulos @sartoric you are obviously in a much better shape than me … SA added 2 secs in every move for me … and really “pushed down” all zones, so that the lowest is no longer visible in the app. Waiting for the fix, no problem.
… Share-button by the way i) works ii) rather laggy iii) the share option does not disappear automatically after sharing the “sporttrack”-link
-
@Shrek3k in the share option getting laggy its android. I bet you have a lot of apps that can capture links.
Same happens also with other apps. Try sharing a text with maps and then again with sa and notice if there are speed changes
-
@Dimitrios-Kanellopoulos yes, Android - and 23 apps are listed in the menu. Sharing menu appearance in (Google) maps is faster (approx 0,5 secs) than in SA (approx 1,5 secs).
And I am not quite sure what and how successful sharing is, as I have sent it from one Android device to another - and both currently available browsers on that device (Firefox and Cliqz) are showing the ST website and endlessly rotating loading circle. I have to try again at home with other browsers and on the PC. -
@Shrek3k thanks
-
@Dimitrios-Kanellopoulos Ascent/descent is corrected, finally!! Good job!
What is still faulty is the shown value in Strava. As I said in another post some time ago, with Suunto I always have more elevation in Strava than in the two watches that I have had and have. With the bike GPS (it also has barometric altitude) I have the same values in Strava and in the device. If I do the same route with the SSU and the bike GPS I got, more or less, the same values of ascent/descent but when it goes to Strava values are higher with the watch in Strava. I’m not sure if it’s a Strava issue.
Anyway, nice to cross this bug from the list!!
-
@cosmecosta Strava is filtering elevation data by their maps.
-
@cosmecosta 2 things. Strava recalculates and Suunto does not send the header in the strava format baro or non baro model