I have GPX files created via a third party App (Memory Map) which when saved/ converted within Strava are showing the incorrect moving time. These are walking activities but much quicker than the 30 mins for a mile quoted for stop timings. Memory Map stop time is fine. I have asked via a support ticket if this can be adjusted in anyway or walk settings, but after a month response did not answer this suggesting that I increase the logging within Memory Map. This can’t be done as I asked them the question which was answered within a few hours, all within the algorithum used so I guess stravas is different. I have raise a query again. I did wonder if its a software standard issue but could not find on the PC. I had seen people were having issues a year ago with moving times?
+26Strava applies it’s own moving time algorithms to third party imports, you can’t do anything about it. The Strava formulas are widely known for their wrong and inconsistent results but complaints about that are ignored for years now.
+1Great! I only use it as I can share with others and it does work out the total elevation climbed which my other tool doesn’t. Frustrating they can’t be honest. It smacks of the help desk not understanding as they do not clearly answer the questions posed to them. All they had to do is say they can’t change it, or would consider looking at it in the future. I’m guessing its no different for premium members or those who don’t use a third party. Still waiting for a reply to the resubmitted query!
Login to the community
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.