(click on flag to translate on your language)

Mismatch Bip data and Strava. Export to Strava trouble.

I have observed a problem in the 1st km statistics when running. Strava will show between 30-40 seconds less for first km compared to what the watch shows, or what you can see in Mi Fit or Notify.

When I export activity to tcx file, I see that first tracking points, aproximately first 200-300 meters, always has same time stamp, and that is causing problems in Strava. So far I dont know if this is a problem of how Notify & Fitness export data, or is the watch that is doing it wrong, any idea?

Comments

  • Same here. I guess it must happen while exporting the data to Strava. In Notify the data seems correct but not in Strava. Is there any solution or update planned?

  • Same problem here, Any update about It?

  • This is a somewhat known issue of Strava. Strava takes the logs that are being uploaded and re-calculates some things such as distance.

    Have a look here:
    https://bit.ly/2q5suMq

    "Unless you are using a Garmin watch, Strava recalculates the data and comes up with its own distance, which it rounds down, rather than using what the watch says. They actually check the data and if it is marked as a Garmin product they use the watch data, otherwise they recalculate everything (and do it quite poorly)."

    and here:
    https://bit.ly/2EzaUud

    "My understanding is STRAVA "corrects" uploaded and recorded GPS tracks on the assumption everyone's tracks wander, but given enough data they can more accurately determine where the route went (and it's actual distance): http://labs.strava.com/slide/ "

    Strava might be the Fitness equivalent of Facebook (regarding the social aspect), with a lot of people on it, but it is a flawed platform. There are much better platforms such as MapMyFitness and Endomondo. Runkeeper does the same annoying re-calculation as Strava.

    I hope the developer of Notify & Fitness includes automatic sync to the Under Armour fitness apps / platforms (MapMyFitness, Endomondo, etc).

  • But the problem is not that Strava recalculates the data , everything is ok except the first kilometer that is 30 seconds less than real time.

  • @dcaguado said:
    But the problem is not that Strava recalculates the data , everything is ok except the first kilometer that is 30 seconds less than real time.

    Does this happen also if you sync to Runkeeper ? Have you tried this to see how that goes?

  • @LostEchoes said:

    @dcaguado said:
    But the problem is not that Strava recalculates the data , everything is ok except the first kilometer that is 30 seconds less than real time.

    Does this happen also if you sync to Runkeeper ? Have you tried this to see how that goes?

    With runkeeper its ok , the problem is only on strava

Sign In or Register to comment.