Two things to fix

Answered

Follow

Piergiorgio Ghezzo

• April 24, 2021 20:55

Hello support,

  two things:

- when the battery status is red, it's impossible to read...

- when I import a track in the dashboard, altitude is too much elevate. (1200m vs 300 real m)

Thank you

3

• 

  Marco Soldano

  • April 25, 2021 14:35
  • Edited

  +1 on the battery status, ran into this yesterday, between the display brightness set to low (to save battery) and the tiny little red font, there's no way to read it, even with glasses.

  I get it you want it to be red, maybe make it withe on a red background and bigger.

  1

  Comment actions Permalink
• 

  Henk Wals

  • April 26, 2021 17:44

  The altitude in the dashboard puzzles me too. Where do these values come from? Make no sense. Not that it bothers me more than the values given on the ride... A sophisticated device as the K2 and his dashboard must be flawless imo.

  1

  Comment actions Permalink
• 

  Jami

  • April 27, 2021 03:37

  Hello all,

  Thanks for the feedback! I have also noticed the battery info can be hard to read in the sun when it's red! I will pass that suggestion on to the developers.

  As for the elevation profiles on the Dashboard, those do tend to be somewhat high relative to some other sites. The issue here is how the numbers are calculated and the algorithms being used. I actually compared several routes across multiple platforms and input the same GPX files to see what kind of variance I got. On a file that Strava and Ride with GPS calculated at just over 4,000', HH had it at 4800' while other sites ranged from 2400' to 4500'. I used Strava and RWGPS as my control because they also use user-sourced ride data and tend to be the most accurate in this respect.

  Our software team addressed on-device ascent and elevation data a few updates back and that has been much better since. We are aware of the ascent discrepancies on Dashboard routes and hope to correct that in a future update as well. Thanks for your patience!

  1

  Comment actions Permalink
• 

  Joel Defer

  • July 07, 2021 19:11
  • Edited

  I did a flat ride tonight. Elevation says 62m. When I watch the ride on the dashboard map, it says 242m. That is a really big difference. 62m seems to be the correct elevation, because it really was a flat ride.

  And why does the imported ride in Ridewithgps have another elevation than my Karoo data? 123m. It’s not the map data, because I can replace my data with the map data, and then I get yet another elevation. 
  
  

  Same ride imported in Garmin Connect reads 101m. 
  
  

  I would think that the elevation data would be the same wherever it’s imported. What’s the logic here?

  0

  Comment actions Permalink

Please sign in to leave a comment.