massive elevation errors when using gaiagps.com web app to plan routes
i am getting strange behavior when creating a routes using the gaiagps.com web app. the routes shows a number of elevation spikes of ~49,000' !!
this behavior occurs on all the maps / layers as well as all geographic areas that i have tried. these are all well mapped and traveled areas.
creating the same route using the gaia iOS app and did not get this error. so i suspect that the error is with the gaiagps.com software for the web app.
others have posted in the community about this exact same issue since at least the fall of 2024. so, this seems to be a well know and persistent issue that gaia / outside are certainly aware of.
any others here (still) experiencing this issue?
anyone know the status of fixing this error which pretty much makes gaiaGPS unusable?
thanks
-
massive elevation errors when using gaiagps.com web app to plan routes… same problem as noted in dacNaut's comment, May 2025. Anyone have a work around or correction??
1 -
i received the below workaround from gaia support. i created a route on gaiagps.com which had the massive elevation errors … i then tried both methods which returned correct elevation data.
_______________________________________________________________________
Our engineering team is still working on this issue. For the meantime, ifcan you please try the following steps and let me know that helped resolve the elevation stats issue:
- iOS: Elevation Lookup in iOS
-
web:
- Click on the route from the Saved items sidebar on the left side of the map.
- From the sidebar, click Open Details Page.
- append
&elevationlookup
to the URL. Example:
_______________________________________________________________________
note: for the web method i needed to append
?&elevationlookup
(note the added “?”) to the end of the address that came up in my browser, which was slightly different that the ones above.1 -
Lol I opened a thread 2 years ago with 20 or so commenta and they never gave an F.
1
Please sign in to leave a comment.
Comments
3 comments