Errors in cumulative elevation are a known issue (really)
There is an issue with elevations shown both in the website and in the app that has been reported numerous times, for instance here, here and here, including myself sending a report via email. To illustrate this better, here's a list of ascent/descent data reported in several places for a route that I planned and tracked with Gaia:
view mode, web & app: ↑784 m / ↓785 m - at least this one is consistent between web and app
edit mode, web: ↑583 m / ↓581 m
edit mode, app: ↑438 m / ↓440 m
GPX track, web: ↑402 m / ↓411 m
GPX track, app: ↑404 m / ↓413 m
I wouldn't care about a few meters of inconsistency here and there but here discrepancies are huge. There has been an update on iOS recently but this problem hasn't been addressed, however, this is not my point. I am very, very sad that despite several reports this has not been included in Known Issues, as it is a really serious one. When planning any mountain hike or bike trip, cumulative elevation is crucial information. You are displaying wrong data to the user and you should be honest about that. Had I known before, I would have waited with paying you for the app.
-
I'm sorry for the trouble this bug has caused.
I have added this issue to the 'Known Issues' section of the Help Center.
Here is the link.
While the more accurate stat is visible in Edit mode, we are still gathering information on this bug in order to find the root of the problem.
Because of this issue, if you would like, we can fully refund your membership. Please click 'Submit Request' above to contact support directly and we will take care of that for you.0 -
Thank you for creating the issue. Could you also make it visible on the main help page? Here: https://help.gaiagps.com
0 -
My Gaia GPS elevation values are consistently 60 feet low (Pixel 4XL). For example, Mt. Bierstadt came in at 14008 when the actual value should be 14063. Sitting here at home, Gaia GPS measures my elevation as -21 when the actual is around 66 feet. It is very annoying and disappointing. I am told it is device specific, and if they fix it for me, it will be off for everyone else. All my other elevation/altitude tools seem to work fine. Why can't Gaia GPS?
0 -
The errors in Gaia GPS elevation gain make the whole computation of elevation gain useless.
I recorded a track mountain biking.
Gaia GPS = 890m elevation gain.
Actual track = 1350m elevation gain. Even if I pin the elevations to the map (removing altimeter errors and noise, as pinning to the map in Garmin maps reads the map from the elevation model), I still get 1350m of elevation gain.
This is ridiculous. It's 50% more. True that the elevation looked like this, but from now on, I wonder whether to just trust my Garmin instead of spending on my Gaia subscription.
2 -
Elevation works until I get to a peak and on the way down it sets itself to 0 and I have to reinstall the app every time to make it work again but every time I use it it'll do this over again. What's the cure for this?
0 -
@Steve
Sorry for the trouble. Your issue sounds a little different than the topic of this thread. I have emailed you directly to help troubleshoot.
0 -
Has this issue been fixed? Most annoying and renders the creation of any route to be somewhat useless and at least, dangerous for us users!
0 -
Here we are two years later and it continues to be a problem. The website data box ascent numbers on a recent route I created are off by hundreds of feet when compared to actual starting elevation and ending elevation. The graph box above it appears to be correct when I compare it to a Caltopo online map. Feel like I've lying to my hiking partners for the last three years. Not happy about this. Why no fix?
0 -
I'm also completely disappointed with this. Not a single track I've recorded has been even close to the correct ascent and descent. This is pretty important with ski touring. Will look for a different app.
0
Please sign in to leave a comment.
Comments
10 comments