"Too fast" pace and distance data discrepancies

I went for a run yesterday and recorded the run with my Garmin Fenix 3 HR.

https://www.strava.com/activities/872864376

I was running with a friend who recorded the run with his Garmin Forerunner 230.

https://www.strava.com/activities/872855492

We ran side by side the entire run.

In Garmin Connect - this run is shown as shorter and with correct "moving time" and "elapsed time" I am happy to email you the .gpx file. - https://connect.garmin.com/modern/activity/1582333209

Specifically, from 14.7k to 15.2k the Strava activity shows me running in the range of an unrealistic 1:00min/k pace. At the same distances in Garmin Connect, these errors do not occur and my correct pace is shown. So the watch recorded the data correctly. Strava software inserted the "bugs" on import.

I have had runs in the past with similar issues, so thought it was time I asked the question.

I also "flagged" this run - which took me off several leaderboards that I like being on. I wasn't sure what the deal with flagging was. Anyway I would appreciate the run being "unflagged" even if the issues cannot be resolved as the overall distance is not way off and is, at the end of the day, the most important stat to me.

Hope this helps resolve what seems to be an ongong issue.

19

Opmerkingen

43 opmerkingen
  • These workarounds don't work:
    1) recalculating distance may correct distance, but in case of error pace will be much more overrated. For example a 6km run at 5'/km was uploaded as 4:20 before and 3:11/km after recalculation. But this happens only when pace is initially overrated, if it's ok also distance calculation is good

    2) Flag activity as a race is a workaround only if I don't stop, else pace will be worser than real

    BTW Suunto Ambit3 disappointed me, the only good thing is I bought it in a black friday at half price

    0
    Acties voor opmerkingen Permalink
  • Suunto to Strava used to work fine - what changed? Did Suunto change the way they record data?  

    0
    Acties voor opmerkingen Permalink
  • I have the same problem I have Suunto Ambit3. Movescount shows the time correctly then once transported to Strava it cuts the time. It looks I am super rapid haha. Is there a solution yet? Don't want to waste time to export every activity as GPX file or mark it as a race.

    0
    Acties voor opmerkingen Permalink
  • Joanna I did get an email from Suunto this morning to say that the Movescount app is being slowly discontinued and the new Suunto App will replace it. Maybe that will solve our issues as mine is also still ongoing using Movescount as well.

     

    0
    Acties voor opmerkingen Permalink
  • Moving to the app won't help. The problem is on Strava side that doesn't parse Suunto FIT files correctly and ends up cutting datapoints where Suunto doesn't specify new ccoordinate. So in short some Suunto datapoints may contain only HR and elevation, but not a new position or speed, and Strava treats those as if you were stopping.

    If you are an Ambit3 user moving to the new app will result in losing a lot of functionality such as sport mode customization, uploading structured workouts, or uploading routes.

    0
    Acties voor opmerkingen Permalink
  • My problem is rather weird.  My friend shared his activity of a half marathon distance we both did together.  I accepted the share and when it appears on my account, although the distance is correct, and the map is correct, it has taken more than 2  hours off the time!  Any ideas anyone?

    1
    Acties voor opmerkingen Permalink
  • I do not use a suunto device but I got the same issue when importing from 3 services :

    - Bryton (I use a bike GPS device)

    - Polar (I record my running rides using polar android app and a polar HR sensor)

    - Amazfit (I own a samrtch watch from amazfit)

     

    The problem is indeed on strava side, since I occurs to me whether I use the auto-sync features from my Bryton/Polar/Amazfit accounts or when I use manual import/export... UNLESS I import a GPX file

    In fact, when I export data manually from any account and import them into strava, the same problem occured in TCX but it seems to be always good using GPX format ... and if a take a look in those files (XML file reader), the data (specifically absolute time stamps) are fine in GPX and TCX files ...

    Whatever algorithm strava uses to fix data, it should never step aside absolute time stamps.

     

     

    0
    Acties voor opmerkingen Permalink
  • Same activity, same device and so the same FIT file:
    Registered as "run" the pace is 4:16/km, as "hike" is 4:47/km (the correct value)

    This means that Strava can correctly manage these activities, for some reason while running some segments are not considered as moving time

    0
    Acties voor opmerkingen Permalink
  • I know the route I run very well.  I have measured it's distance on a map.  I know how much time elapses during my runs.  I never stop and maintain a fairly steady pace.  Armed with this stunning array of common sense metrics I can calculate my moving time and average pace.  I can do what math is involved in my head.

    Both the old and new Suunto app consistently report accurate results.

    Strava reports inaccurate results which consistently appear as if I am running significantly faster than I actually am.  Moving time is incorrect as is pace.  Ironically, the map of the route and the distance reported look correct.

    I did notice that the problem got significantly worse when I changed my watch from 1second data points to 10second data points.  Perhaps the decrease in the number of data points greatly increases the impact of data gaps on the Strava algorithms.

    Regardless, the smart folks at Strava have access to the same data as the smart folks at Suunto.  So clearly it falls to the folks at Strava to address these problems.

    That said, it you want to boost your placement in the leaderboards get a Suunto and drop to 10s interval recording.  I would think Strava should take this very seriously.

    0
    Acties voor opmerkingen Permalink
  • Recent problem for a recent run, I noticed with Strava app, the live recording was saying my time was 30 minutes.  I press Finish, save and the segment in Strava indicates total time of 24 minutes with an unreal pace.  Why is strava removing 6 minutes from the actual time that its app was showing in Strava before pressing finish.  Really odd!  I haven't figured it out.

    0
    Acties voor opmerkingen Permalink
  • I have noticed over my past few runs that the lady says my average pace over that km but after I upload my run the average pace is a lot slower. Have started using my Fitbit Versa to upload to Strava instead of my iphone as that has more of an accurate pace. Can someone help or tell me why this is happening

    0
    Acties voor opmerkingen Permalink
  • I have Suunto 9. Same issues as the rest of the Suunto owner runners. 

    Is there a solution for this issue or we just give up on Strava? Not sure what to do - I love to run but I am not the world class runner as Strava makes me to be - it is actually very uncomfortable for me to post the time on Strava - it's wrong.

     

     

    0
    Acties voor opmerkingen Permalink
  • same problem with all runs from samsung galaxy active, short moving times, very high pace. wild spikes in pace graph

    have to set run to "race" every time which is annoying.

     

    0
    Acties voor opmerkingen Permalink

U moet u aanmelden om een opmerking te plaatsen.

Niet gevonden wat u zocht?

Nieuw bericht