Strava-Speed-Graph (Analysis) has huge jumps since recently

Answered

Follow

Tobias Zeh

• May 27, 2020 11:10
• Edited

Look e.g. here: https://www.strava.com/activities/3515412469/analysis (but not only that activity, many [but not all!] of my recent rides. You can access them all, they are public: https://www.strava.com/athletes/32453890 )

There are e.g. jumps from about 35km/h to 50km/h and then back to 35km/h. And no, I didn't accelerate / braked that fast, I was riding smooth. And the values displayed when riding didn't jump that much. I had this problem before when I used a speed-sensor https://support.hammerhead.io/hc/en-us/community/posts/360037797494-First-impressions-several-big-and-small-problems , but after switching to the internal GPS-sensor for speed/distance it was gone. Now it's back again although I'm still using the internal GPS-sensor for speed and distance. 
What can I do to avoid this mess?

4

• 

  Hari Krishnan

  • June 02, 2020 09:10

  Hi Tobiaz, Sorry for the inconvenience caused to you. I have created a support ticket requesting for some additional information to look into the issue. I request you to follow-up there.

  0

  Comment actions Permalink
• 

  Anders

  • June 10, 2020 04:32

  I too am experiencing this now. I was out riding yesterday where my recorded top speed was 58.8 km/h but Strava said it was 65.5 km/h. In my experience the jumps are not as pronounced as when using a speed sensor but they are still there. Tobias did you find a solution?

  0

  Comment actions Permalink
• 

  Tobias Zeh

  • June 14, 2020 08:26

  »Tobias did you find a solution?«
  
  Hi Anders, 

  unfortunately not. By request, I sent the corresponding fit-files to the Hammerhead-support, and their answer was:
  
  »(...)
  I checked with the software team and they confirmed that they are aware of this issue. The fix for this issue requires a combined effort from us and Strava and the Product team will look into this. Right now, I do not have a dedicated timeline to share with you as the Product team is working on the implementations on the existing backlog. I hope you understand.
  
  I appreciate you patiently working with me and providing all the information needed to escalate the issue. I will be closing out this ticket but I have attached all this information to the master ticket raised with the Software team and raise this as an issue that warrants a fix.
  (...)«

  I'll write the Strava-Support as well when I find time/leisure to do this. Maybe they have an idea/solution.

  At least, it doesn't happen most of the time, when I don't use a speedsensor. (With speedsensor, it happens 100% of the time, and even the before working-sort-of-a-fix use Strava's distance correction doesn't work anymore unfortunately.)

  0

  Comment actions Permalink
• 

  Anders

  • June 17, 2020 08:07

  Hi Tobias

  Thank you for the answer.

  Regarding writing to Strava, I will not expect any answer in the near future. I actually tried writing to Strava a while back about this issue, but I never recieved an answer even after about three weeks wait and then I recieved an email stating that my support request would be deleted if I didn't answer to that email, and by then I was no longer experiencing the issue so I chose not to answer, which in retroperspective was a bad decision.

  Best regards Anders  

  0

  Comment actions Permalink
• 

  Tobias Zeh

  • June 17, 2020 08:19

  Oh, that doesn't sound promising...

  On a ride yesterday, I discovered, that right in the ride the behavior of the speed-graph changed from acceptable (anyway with some jumps) to really bad after a stop on a traffic light:

  

  That's https://www.strava.com/activities/3624764643/analysis/21039/22106 
  Maybe it's some GPS-inaccuracy? 

  0

  Comment actions Permalink
• 

  Tobias Zeh

  • June 17, 2020 09:58

  Filed an Strava-support request: https://support.strava.com/hc/de/requests/1703597

  0

  Comment actions Permalink

Please sign in to leave a comment.