3 Weeks in and realized the elevation is a total joke. Refund???
Finally retired my Garmin 510 for a Karoo2. Comparing exact rides I am seeing 30% higher elevation gain with the Karoo2. Did I mention I hate climbing - I would never knowingly add more elevation to a ride.
For example a 40 mile coastal ride in California I have done many times is consistently 1275-1290 feet of elevation. Karoo says it is 1690!!!
Seems like this is a known problem for a few years - where is the fix?
-
This is the difference between the same route in Garmin connect and Hammerhead dashboard. The climb planning aspect of the Karoo is absolute hot garbage, although I find the en route elevation readings by the device accurate enough. According to my experience and measurements done using other devices and apps, Garmin connect is very close to what the final elevation ends up being. This issue needs to be fixed, it is driving everyone insane.


-
New owner of a K2 here. I've owned the K2 for about 6 weeks or so now. I've known about the elevation discrepancies between what the K2 calculates and what Strava calculates, but still went ahead and bought the K2 as the difference (though not insignificant) will not necessarily "ruin" my riding experience.
At the end of the day, dare I say most of us are not dependent on having very accurate data - as in it won't stop us from riding. I know we all want to have as accurate information as possible.
Here is my data for the 16 rides I've completed so far. An important point to note is that none of the routes are complicated MTB trails that are not mapped in Strava. Every single route here is mapped on Strava and RideWithGPS. In summary, the data can be off by as much as 26% (the K2 "padding" the numbers ) and in one instance it was under by 29%. I consider that data point an outlier, however the rest of the discrepancies confirm what you read online about this Achilles heel of the K2.

Please sign in to leave a comment.
Comments
6 comments