This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Strava (not Garmin after all) broke climbpro

jgforrest
over 1 year ago

I've seen a few posts on this and made some myself, but I now have conclusive evidence that Garmin have broken climbpro in the transfer of routes from Strava (and maybe other platforms) to Garmin Connect.

The problem is that Garmin recalculates the elevation data, but makes a mess of it. The image below is the elevation of the same route (via GPSVisualizer), one trace is  from Strava, and one is from Garmin Connect after transferring it through the API (favourite the route in Strava and it comes through automatically).

Heres the Garmin vs Strava elevation at the start of the route

and here it is at the end

Heres the full trace, at the start of the elevation profile its fine, at the end its way out.

  • 0 over 1 year ago in reply to aweatherall

    I’m not sure it’s a compounding data error just because of a lot of points if that’s what you mean. I think it might be missing data points due to a calculation error as the distance between points approaches 0. The distance isn’t constant, there are some data points as close as a metre apart and I think that might be where the errors are creeping in. 
    the error tends to jump at certain points, rather than be linear. 

  • 0 over 1 year ago in reply to aweatherall

    I too had problems doing "We Ride Flandres" and Climb Pro, it was way off, and to no use as such. Had the course from the organizers web page unto Strava and then synced with Garmin Connect.  Ride seen here :  www.strava.com/.../8813294883

  • 0 over 1 year ago in reply to jgforrest

    It appear that the points closer together are likely causing bigger issues. There are 190 points that are less than 1 meter apart. A precision issue would not have to generate a linear displacement depending on how values are rounded or trimmed. Some values could under report the distance and some values could over report the distance. The displacement is the accumulation of the under and over values.

  • 0 over 1 year ago in reply to aweatherall

    With the data points I can now go and calculate the distance between them and play around with removing points that are close together and see how the distance changes.

  • 0 over 1 year ago in reply to aweatherall

    Yup I agree that the points being so close might well cause issues . I saw errors when I imported the data into excel and used the points to calculate the distance. 

    I think one way of isolating it would be tweaking the course data loaded via the API. I have access so will have a crack if I find the time. 

  • 0 over 1 year ago in reply to jgforrest

    I have a spreadsheet set up to do distance calculations from the course Lat/long data. Let me run the course data through it and see if I get a similar total distance value.

  • 0 over 1 year ago

    Hello. I have also experienced lag on ClimbPro. And have tried to create several routes on Strave which I have transferred to GC, and then downloaded a GPX file from Strave and a GPX File from GC after transfer in API. I can't get the error. I tried the Flanders GPX route that is in this thread, and then I get the error. But when I force Strave to recalculate it, by editing the endpoint and saving it as a new route, syncs it over. Then the routes are in perfect sync again.
    EDIT: I'll also did a test with RwGPS, and the route are in sync there too.


    So then I wonder if Garmin this week has fixed this now? And that the video of GPLama has had an effect?
    And a great thanks to Jeff -- jgforrest  for "proof" of this error.

     

  • 0 over 1 year ago in reply to b1ue3AGLE

    Thats weird. Your graph looks fine, but the error still exists for me. I also tried with my wifes Strava/Garmin accounts, using the Tour of Flanders route and got the same offset in the Garmin file so its not just me :-)

    A route I rode yesterday saw the same issue too. All very strange.

  • 0 over 1 year ago in reply to jgforrest

    Digging into the Tour of Flanders gpx files I can see where the offset is happening, its a step rather than gradual and it happens noticeably at 20.1km, at 54.3km, and again at various points, but I can't see any smoking gun reason why. I thought it might have been errors from distance between points approaching 0 but that happens fairly regularly and the Strava data even has duplicate points that don't correlate with the offset.

  • 0 over 1 year ago in reply to jgforrest

    Try this:

    • Make a copy the Tour the Flanders route on Strava.
    • Star it, and download both GPX files. You will see the offset in the GPS Visualizer.
    • Then edit the Copy of Flanders route, by changing the endpoint, route typer etc,
    • Unstar it, and restar it to resync the route to GC.
    • Download the GPX or FIT files again. And compare them with GPS Visualizer.

      In my case the route is in sync. I'm hoping that Garmin have fix the bug this week?
      Maybe this happen because the route is catched in the API?
      All my route that have been sync the last 2-3 years from Strave or RwGPS have had this lag. If it's fix, it moust have been done lately.

      EDIT: I tryied this againg today, and the LAG is back on the Flanders route. Stranges.
      EDIT: Other new routes, that is created fresh today are in perfect sync.