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

Course Elevation Plot data from GPX or from Map?

I ran a course I uploaded yesterday and all the elevation data seemed accurate however when I look at the elevation plot, it is way off.  Viewing the course plot on the watch during the activity it shows a starting elevation of 7301' and max elevation of 9285'. However it shows an ascent of 8408'!  The true ascent was 2133'.  The climbpro vert was also way off. I assume the GPX data is bad.  

What would be the easiest way to calibrate the correct ascent numbers in the course?  I can't find a way to view the actual GPX ascent data points outside of the watch.  Also, I assume that the ascent and climbpro data can only be ran from the initial GPX data and not the actual map from the watch?

  • Do you have the gpx-file your self?

    You can open it in a text editor to see if there are any <ele> in there at all.

    Open http://www.mygpsfiles.com/app/ and drag your file into it and then you can see a graph of the elevation. It also shows (what I assume are calculated) E+/E-. To my knowledge, gpx can't contain ascent/descent values. My test file that I just used, didn't contain it and it shows E+ and E-..

  • Interesting. I uploaded the GPX to the site and it shows the correct E+/E- data and searched the text but nothing looks out of ordinary. Now I'm really confused.  Here is the Elevation plot:

  • I see a lot of mini spikes in the watch graph. Can it be that the watch adds all those? Maybe MyGpsFiles smooth it before calculation. Can you see those mini-spikes in the text file?

  • Yeah, odd but the data isn't showing that variation on the text file. I've put in a ticket with Garmin to see if they can figure out why it's so off.

  • this only happens to my if i import a course via garmin connect. the elevation data is ridiculous. if i import the same course via the komoot connect iq app, the original elevation data that also feeds into climbpro is correct. that's why i am using this workaround. something with gamins algorithm is broken?! i am also seeing these spikes.

    i also started a discussion - including pictures here: 

    https://www.dcrainmaker.com/2020/05/garmin-launches-strava-komoot-route-sync-works-on-devices-a-decade-old.html#comment-3562253

  • Thanks DanielM!  I’ll try Komoot.  I never heard back from Garmin support and gave up but, the issue is still there.

  • I often have the same problem. Try to upload the GPX file with GarminBaseCamp instead GarminConnect

  • I see only small differences. Typical example is:

    I draw a cycling track with the app Locus Maps (Android), than export as GPX-file and import into the GC Mobile App: 445 meters. On the watch the elevation plot says 364m. There is no difference whether the drawn GPX-file includes elevation information or not. So both Garmin Connect and the watch calculate the elevation. In most cases the difference is only a few meters.

    I ran a speed-hiking trail last year and the GPX-track was provided. It shows 1080m on the watch, 1126m in Garmin Connect and after the run the measured elevation was 977m.

    So overall I only see values which are in a normal range of error and I never saw something like factor 4....