Elevation still not correct after latest update today
-
Ok so here is yesterdays ride with the last software release from a week or two ago. You will see uploaded to RWGPS, Komoot, Strava and K2 Dashboard. The differences in elevation are not crazy but none the less they are all different, 4025’ to 4226’. Oh and the original route was created with RWGPS, elevation is 3981' The ride was recorded with the K2 and then it uploaded to the other three apps plus Dashboard. Ponder away.
-
You should start by assuming that all of them are simply projections and most likely incorrect.
Then try manually calibrating your K2 based on your ride start point. I recommend using https://whatismyelevation.com/ for this. I've had variable results when using auto-calibration on the K2 so try manual calibration first of all; it's easy to do providing you have an internet connection (tethered/wi-fi/cellular all work).
I have compared elevation spot heights on an Ordnance Survey map (I'm in the UK) against the elevation readings recorded on the K2 and I've found them to be highly accurate. Do the USGS publish something similar there?
It's easy to blame the K2 when your elevation gain doesn't match Strava/RwGPS/Komoot and any other services that projects elevation gain based on a basemap. The reality is that they are all probably as inaccurate as each other.
Yesterday, for example, I did a shortish 50 km (31 mile) ride with a recorded elevation gain of 479 metres (1572 ft) and when I ran Correct Elevation in Strava my total elevation gain was within 5 metres (16 ft) of what my K2 recorded (which equates to a ~1% variation) for that ride.
Even looking at your own elevation figures, you're still talking about a ~5% deviation, which I consider acceptable for a ride of of that length and duration.
-
Hi Guys,
to be honest, I think this is the completely wrong approach. OK, so I have a device, but just assume, the data is incorrect.. so why would I use it anyway?? Oh, my navigation system is not accurate, so just don't look at the ETA or so.. or just take another device.
A discussion like this is just not appropriate. There is a basic function of a bike computer and this should be correct. Its not that hard. Skip developing fancy other stuff and fix the basics. Who cares if the Radar line is a bit optimized now, or a change of a data field at the climber.. seriously.
And yes, there is always a slight difference between Strava and Komoot f.e. But its maybe like Strava has f.e. 550hm, and Komoot then maybe 549hm. So it is almost the same. But Karoo would show 1150hm or so.. completely way of. But the elevation of a ride is ok. Just the one of planned routes are way off.
-
Just to prove my point - and for a bit of fun (!) - I created the route I rode yesterday in a couple of route planning apps. Here are my elevation figures for the route I rode:
- Komoot (as planned): 380 m
- RwGPS (as planned): 532 m
- Strava (with elevation correction applied): 484 m
- Strava (route planner): 489 m
- Karoo 2 (as recorded): 479 m
- Hammerhead Dashboard (as reported): 448 m
So, which one are you telling me is correct? How can there possibly be a 152 m difference between Komoot and RwGPS? I don't regard this as a "slight" difference; this is a 40% difference!
This is NOT "almost the same"; I stopped relying on Komoot and RwGPS elevation projections a long time ago.
I stand by my assertion that "they are all probably as inaccurate as each other".
-
@ Steve
They're referring to the elevation shown for _routes_ in dashboard (and on device), not recorded rides (which is indeed fine).
The former is, just like they say, pretty much double what any other source says, vary as they may. This is bad and should be fixed, period.It doesn't impact me in the slightest but I can see how it'd be worse than annoying if living in the mountains, having many routes of which some created on the dashboard, some externally, and wanting to pick one based on elevation.
-
Yes, I know they're referring to Routes in the Dashboard. Did y'all read the release notes for the latest software update?
Dashboard Software:
- We’ve improved our Total Ascent calculation for routes and rides on Dashboard.
- Note: Total Ascent is recalculated by Dashboard when you import a route, so the value shown can differ from the calculations of other software services for the same route. Total Ascent is also recalculated for rides uploaded from Karoo, so the value shown in the Ride Detail on Dashboard can differ from what the Karoo’s barometric altimeter recorded to the FIT file. This does not affect the value in the FIT file for the ride.
The important line here is, "Total Ascent is recalculated by Dashboard when you import a route", which is why this thread exists because Paul believes the "elevation on Dashboard and K2 is still wrong on already imported routes and also on new routes imported from Komoot."
Like I've already said, the elevation data provided by Komoot is mostly junk (see my example above where there is a 40% variation between Komoot and RwGPS). Please do not compare elevation data in the HH dashboard with elevation data from Komoot and then come to the conclusion that the HH Dashboard /Karoo is wrong and Komoot is right. You don't know that. They are all as inaccurate as each other.
For me, the Dashboard is simply a hub for getting routes onto my Karoo from my connected services and for publishing rides I've completed to my connected services.
-
Hello,
I have noticed this discrepancy also, but for a recorded track.
The following picture is for a recorded Hiking tour on K2 on dashboard:
Next is the same data uploaded from dashboard to kommoot
Which is pretty much the double amount....
And the same track data in GPXSee
This is quite near to komoot.
So this is not a callibration error, since the data are shown correct for the GPX Data Point in Komoot and GPXSee.
The reason for this may be lying in the calculating of the tour data given by the K2 device.
The K2 also shows the same data under "rides" menu.
If I reimport the exported FIT file it shows the following:
Maybe I gain some extra elevation during the tour but 300m?!?
And as you can see, this is double the value of the K2 Device.
So, something went wrong with your calculation.
Best regards
Markus
-
Update of today.
I have recorded a hiking tour to the Katzenkopf at Garmisch Partenkirchen.
And it is the same as bevor and nothing is really changed with the update.
This is what the dashboard at Hammerhead shows:
Next picture is at komoot after using the transfer button out of the hammerhead dashboard:
The same as the dashboard.
After exporting and downloading the GPX/FIT track from the dashboard, a reimport to komoot shows the right data:
These are the right figures. Same result for any ohter GPX analysing software beside of hammerhead.
There is definetily a bug in the Software of the dashboard and/or the Karoo 2 Device.
If any one wants to have the Data, I got no problem to share them.
Best Regards
Markus
Please sign in to leave a comment.
Comments
11 comments