Bug: Strange spikes in altitude data

Answered

Comments

11 comments

  • Avatar
    Anna Ronkainen

    Looked at the data in TrainingPeaks as well and most (but not all) of these spikes seem to be associated with sudden changes in temperature:

    0
    Comment actions Permalink
  • Avatar
    Edgar Karel

    Interesting observation, since HH calculates elevation via a barometer. And temperature will influence the barometer.

    0
    Comment actions Permalink
  • Avatar
    Anna Ronkainen

    Yeah, that’s what I thought as well. Still, it being anything weather-related doesn’t make any sense to me, because here’s another ride from about two weeks ago in extremely challenging weather (wind gusts well above 20 m/s, should not have stopped reading the forecast at “no precipitation”...) in Finland, and the temperature and altitude data seem completely normal (apart from the lack of altitude calibration):

     

    0
    Comment actions Permalink
  • Avatar
    Ali

    Hi Anna, we are working on smoothning and filtering out the spike with the elevation data. May I know if you were using the SIM card on your Karoo without or without a cellular data ON?

    0
    Comment actions Permalink
  • Avatar
    Anna Ronkainen

    Thanks for the info. I generally have cellular data on (including on these rides), except when there might be a risk of downloading additional (unnecessary) offline maps (I think this one has been fixed but I’m still a bit paranoid about it).

    0
    Comment actions Permalink
  • Avatar
    Ali

    Anna, could you disable that on your next rides and see if this still continues to happen? We are still working through these as it has been challenging but we are committed to get it solved.

    0
    Comment actions Permalink
  • Avatar
    Anna Ronkainen

    Ok, I’ll try it, but again this only seems to be happening to me in Germany (and not Finland; mobile data on in either case), which is kind of strange.

    0
    Comment actions Permalink
  • Avatar
    Anna Ronkainen

    I checked that I have automatic calibration on (must have somehow failed in the ride that was recorded as being all below sea level) and it says something about using the internet connection and what else, is the unit really doing something too smart for its own good in terms of altitude calibration? I would think that doing it at the start of the ride (or once every 3–6 hours) would be enough, after all we’re not trying to land an airplane here or anything...

    Anyway, I’ll try both turning the mobile data off and switching to manual calibration.

    0
    Comment actions Permalink
  • Avatar
    Anna Ronkainen

    More experiments done (expected altitude gains according to Komoot, with some margin off error due to deviations from planned routes):

    1. mobile data on, automatic calibration on: 500–600 m expected, 2372 m recorded
    2. mobile data off, automatic calibration on: 250–350 m expected, 450 m recorded
    3. mobile data on, automatic calibration off: 350–400 m expected, 1617 m recorded
    4. mobile data off, automatic calibration off: 300–400 m expected, 628 m recorded

    I guess the winner is option number 2.

    1
    Comment actions Permalink
  • Avatar
    Steve MacMillan

    That is a very disheartening set of results! Thanks, Anna, for taking the time to do those tests!

    0
    Comment actions Permalink
  • Avatar
    Antonio Prado

    The same is happening to me. I'm getting mistaken altitude numbers due to the peaks.
    I'm using sim card with data on

    0
    Comment actions Permalink

Please sign in to leave a comment.