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

Problem with elevation on Garmin Connect Segments.

This is an example of what occurs when I try to ride Garmin Connect Segments with my Edge 820 (firmware 12.70).

I think it happens when points of the segment's FIT file don't have a value for altitude.

Any help to fix this is welcome.

connect.garmin.com/.../5A6253FF1E674295AF1202D1270AC2E9

  • I have the same problem on my Edge 520 plus (5.70) :

    The altitude of the segment is displayed correctly both on my Garmin Connect web page and on my phone, but when loading it on my GPS, it has the same output as your pictures. Did you find a way to fix it ?

    As far as I can remember, in my case, the problem first appeared in April I think, before that everything was OK. I also can add that the segments that I created after one of my ride (through the activity section of my Garmin Connect page) have the same problem.

    I contacted Garmin support about it : first, they told me to reset the device, but that didn't change anything. So they sent me a new GPS (mine was still under warranty) but it has the same problem.

    If anyone can help on how to fix it, I would greatly appreciate it.

    Thanks.

  • I would suggest deleting the segment off the Edge and pushing it again from Garmin Connect. There was an elevation fixed deployed by Garmin on 2021-07-01 for courses that I think might also impact segments.

  • Thanks for you reply. Unfortunately that didn't work for me : I deleted all the segments from my device, installed a few of them back on it. I also tried creating a new one from a ride I did on July 14th (without my GPS since I returned it back to Garmin at the beginning of July for support) but no chance : still the same problem.

    I'm wondering whether the problem of the "scale on the Y axis" (5037m on the picture in the original post) is a cause or a consequence of the bug.

    Also, if that's of any help, I tried switching from meters to US units, but the problem remained.

  • Could you either post the segment file or the URL for it and I will take look at the data.

  • I checked 4 or 5 differents segments (some I created, other were already existing) and they all have this problem.

    One of them is this one for instance : https://connect.garmin.com/modern/segment/40AF170988684CE48DF6A2FCA2A205E8

    It displays properly on the Connect web page and also on my iPhone app :

    But on my GPS it appears like this :

    Another segment for instance is this one : https://connect.garmin.com/modern/segment/0895976A95F047309A27FFEEC25DE985

    Thanks.

  • Ok I see the problem. Some of the records have no elevation data. Let me pass this on to Garmin.

  • Cool, thanks. Hopefully this can be fixed quickly/easily.

    I hope to know where this problem has come from. Like I said in an earlier post, everything was fine until around April. I don't think the segments have "changed" (can they?) so I thought maybe it was because of a firrmware or map update... But in that case, I guess there would be more people with this problem.

    Thinking

  • I couldn’t say when it started, I’ve found this after a very long time without using the Garmin.

    In any case, thank you for relaunching the subject. Hopefully a fix is on the way.

  • I don't know if it's of any help to understand the problem, but in my Connect settings, the "elevation correction" ("Corrections d'altitude" in French) parameter is "disabled" on my GPS (I think it has always been, but just in case, I thought this could be worse mentionning.