Incorrect distance and elevation

Comments

6 comments

  • Avatar
    Seth Challenger

    If you watch the "Current Elevation" screen, the altimeter is working flawlessly--  just whatever code they're using to determine total ascent is...  not working.  Mine reports about 1/3 of actual. But Strava corrects to to actual, which is about 10-15% over what my Garmin has been reporting as of late.  The Garmin got mice and wet a few times in it's service life, and has been gradually robbing me of more and more elevation (confirmed by doing the same routes multiple times, and watching the total ascent gradually lessening.) 

  • Avatar
    Steve Hammatt

    That's interesting, Seth. I only had the total ascent field enabled, so I'll certainly be adding the current elevation for my next ride.

  • Avatar
    Luis Weber

    As far as I know, Strava does not accept the barometric output from Karoo yet (I can confirm the FIT file from Karoo does contain the correct elevation from the barometric sensor). I recorded a ride yesterday with a multitude of tunnels and bridges, which without barometric sensor are just turned into 0 elevation in the Netherlands. The Karoo FIT file however showed dipsup to -20m and tops up to +30m at those critical locations. (easy here in Holland, all is flat except tunnels and bridges!). 

  • Avatar
    Michael Lowden

    No one has mentioned if they are only using the auto set feature for the altimeter basis. Mine was off by approx 200 ft, showing about 1750 ft at my location when I am actually 1550 ft. I have set it manually and will check to see how it interprets it in the ride. On my last ride, with it set to Auto, the in ride elevation gain was wrong, but when it shipped to Strava, looked ok. 

  • Avatar
    Michael Lowden

    After manually setting the elevation, the ride still shows only 63 ft of ascent. After upload, it showed 294 ft versus 325 upload from my Wahoo Elemnt. But on the Karoo activity screen, it only shows the 63 ft, or about 20% of actual.

  • Avatar
    Steve Hammatt

    The current climbing/descent data is way off, though the current elevation field seems to be accurate. To be fair to HH, they did stress on the livestream that the climbing data would be in beta, and these fields are labelled as such when you choose to add them from Karoo, and HH implied that they'd need to tune how the algorithms work to present this data (I imagine there's a lot of smoothing out to be done).

    Setting the elevation manually will help the elevation data field start from the right base point, but it won't help at all with the climb/descent data.

Please sign in to leave a comment.