For at least a year, the elevation profile has not read correctly while recording a track. I live in Colorado, so I'm generally recording in the 6,000'-14,000' range. When viewing the elevation profile while recording a track, the rightmost edge of the profile (current elevation) always shows a huge drop, often displaying the current elevation at 2,000-3,000'. This anomalous data point (which disappears once the track has ended) renders the elevation profile useless while recording.
I've tried emailing support about it numerous times and gone through a lot of back and forth but have not seen any progress on resolving the issue. Displaying an accurate elevation profile is basic functionality that I expect from a mapping app, and despite my love for Gaia, I've begun researching alternatives. I'm not a programmer but I can't imagine that squashing this bug would require significant effort.
I see the exact same behavior on both a Pixel 3XL and an S21 Ultra.
Please sign in to leave a comment.