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

Elevation Tracking Off, Spiky Graph

Love the 245. But after three runs, I've notice that elevation tracking is off compared to my old vivoactive 3 hr music.

It will says I've done much more elevation than I should have, and the graph is spiky, as if I've done lots of steep up and down hills.

I've attach graphs of two runs doing same exact course, one with the vivoactive hr 3, and the other with the 245. The vivoactive is much smoother, and accurately reflects elevation changes. The 245 says I have done 1,676ft in elevation change, while the vivoactive is only 715ft.

I am using GPS + Glonass.

I would love any ideas for how to fix!

Software version: 2.60
GPS: 2.30
CIQ: 3.0.10
BMX: 0.4.8
WHR: 20.04.12
ANT: 3.50
Sensor: 2.30


ciq.forums.garmin.com/.../1479302.png ciq.forums.garmin.com/.../1479303.png
  • The 245 does not have a barometric altimeter, which was providing elevation data on your Vivoactive 3M. I would guess that you are seeing some GPS drift on the 245 which will cause elevation spikes, particularly if you are running on a canyon trail (or any route along a hill). Depending on where you are running, you might see significant improvement by "soaking" the gps (wait a few minutes once the gps signal shows ready) before you begin your run. Without the altimeter, you are relying on good gps tracking to supply accurate elevation data.
  • I see. I did try "soaking" after noticing it on my first run, but it did not help. I compared the GPS maps from this run with lots of previous runs on the Vivoactive 3M, and they are all drifting to some degree. I've tried all variations of GPS, GPS + GLONASS, GPS + Galileo, soaking, to get accurate GPS tracking, but it's always off to some degree and never perfect.

    I really do need (semi) accurate elevation tracking, so looks like I will be returning and upgrading to the 645.
  • Assuming those charts are from Garmin Connect; they should have been automatic elevation corrected since the 245 doesn't have a barometer. (https://support.garmin.com/en-IN/?fa...Uk8gJPC4zi0Xv6). Do some research on the 645 for there has been some complaints on the elevation (they may already be resolved). I would stick with the 245 just for the Sony GPS chipset (much better battery life).
  • Hi kgarten, I do see that automatic elevation correction is being applied. It is actually what's apparently causing the spikey graphs, because the GPS drifting makes it look like I am running up and down the topologically-precise hillsides, not along side it. When I disable automatic elevation, it is less spikey, but still very inaccurate, compared to barometric readings.

    I read your thread on elevation issues with the 645. That is sad. My vivoactive 3m should not be the superior product when it comes to (mostly) accurate elevation tracking.

    It's a bit unfortunate that Garmin has such a complex line of products. I thought for sure the 245 would be a very good watch for running, at least better compared to the vivoactive 3m. In many ways it is, but inaccurate elevation tracking is a big step back, and show stopper for me.
  • Too me I find the elevation corrected activities to be spot on. Even some of the Fenixs use their topographical maps to record elevation. This is a nice feature for me on my 245! But I'm also coming from a VA3 which had bad elevation/barometer drift. I've heard that the VA3M barometers are much improved.
  • Former Member
    0 Former Member over 5 years ago

    My 245M and Garmin Connect shows altitude of 75-78meters on a hilly excercise. 

    Same excercise in Strava has altitude 83-113meters and elevation gain 84m wich is more close to actual. 

    What can I do? 

  • Any solution? I was on the 235 that went dead after 1.5 years. Just got the 245. I run a flat route. 235 always had 80 to 100ft elevation gain. Now my 245 is reporting 800 to 1200ft elevation gain. Something is seriously wrong with the 245 and elevation gain! How can fix?