Dashboard > Inconsistent elevation reporting
Planned
There seems to be some inconsistent reporting of elevation for the same ride in the "Recent Rides" tile and the actual ride drilldown data.
For example, in the "Recent Rides" tile, today's ride elevation is given as 335m. When I drill down into the ride data, the value at the bottom of the screen now says 453m.
Same for the previous ride. Recent Rides tile reports that as 436m but when I drill down into the ride details, it is being reported as 538m.
Every single one of my rides exhibits completely inconsistent data between the Rides list view and the Ride drilldown view.
Why the discrepancy?
Surely you should be using the same data point to populate these values?
-
I don't believe this is the case, no. But it's possible you've discovered another discrepancy across different web browsers. I'm using Chrome 88 here, FWIW.
If it was the starting elevation, it would show 60m since I know that the elevation of my house is 60m above sea level, via https://whatismyelevation.com. My Karoo 2 also indicates that my elevation here is ~60m via the auto calibrate elevation function. All of my rides start from home and I would expect the Elevation field to show 60m for every ride if this was the starting elevation.
My understanding is that the Elavation field is supposed to display the total elevation gain of the ride. This post is simply pointing out that there is a bug concerning the inconsistent elevation reporting in two different views in the Hammerhead Dashboard (when it should just be GETting the same data point and populating it in the UI).
-
I just wanted to provide some more data on this particular issue to help you guys resolve it.
I took my Karoo 2 for a short "there and back" walk to the shops at lunchtime today. It was approximately 1.50 km there and 1.61 km on the way back (presumably due to crossing roads, etc...) according to my Apple Watch.
This is what I found:
Karoo 2 Ascent (Ride Summary Screen) = 72m
* Please also note that AVG HR is displayed for this walk, even though I wasn't wearing a HRM at the time. It's possible the connection to my Polar H10 had remained active from when I re-paired it with my Karoo 2 earlier this morning. I have reported this issue previously but it looks like it's not been fixed yet.
Hammerhead Dashboard Recent Rides Tile = 73m
Hammerhead Dashboard Ride Drilldown Page = +27m
Apple Watch = 36m
Of those values, the one I am most inclined to believe is correct is the data provided in the Ride Drilldown page (+27m). It wasn't an especially hilly route.
I've just checked on whatismyelevation.com my starting elevation and compared it with my destination elevation:
Starting Elevation: 60m
Destination Elevation: 51m
These values are also supported by the Ordnance Survey map for my area so I consider them to be accurate.
I'm assuming that the "Ascent" value in the Ride Summary Screen on the Karoo 2 is the total ascent gained on the ride/walk? There's no chance it was anywhere close to 72m.
I'm assuming that the "Ascent" value in the Ride Drilldown view is calculated and supported by the base map in the Dashboard (which is why it's probably a more accurate value)?
Anyway, I hope this data is of some use and enables you to resolve this issue soon.
Steve
-
One thing I've noticed about this issue is that the problems only become apparent when the Hammerhead Dashboard gets involved. Either by importing a route from another source or by viewing a ride you've already completed.
It almost looks as though the values are being incorrectly calculated or perhaps the basemap - containing the elevation profile - is wrong.
I did a ride this morning which my Karoo 2 recorded as 333 m of climbing. When I drill down into the ride, the value reported at the bottom of the map is very different:
Really, I want to be seeing consistency across the distance and elevation fields here. There is no good reason for these values to be different. You should be using the same data point for the Rides summary view and the Ride drilldown view.
Somewhere, along the way, I've gained an additional 111m of elevation for some reason. This happens consistently with every ride I import into the Dashboard.
BTW, Strava corrects the recorded elevation gain to 324m. My Apple Watch recorded it as 319m.
-
Running K2 and Garmin Edge 130 Plus side by side on today's ride.
K2 ride uploaded to HH Desktop reports 279m elevation on Ride Summary Tab, Garmin Connect reports 267m. Near enough in agreement. Strava echos the Garmin Connect value exactly - it auto uploads from Garmin Connect apparently without any 'fiddling'.
'Opening' the ride on HH Desktop shows 451m total elevation gain (and loss - ok, it was a circut). The HH Desktop detail view still appears to be broken.
That Dashboard value seems to be suspect. -
This is mostly true, but you can also attempt to correct your elevation in Strava if you think it's wrong. Yes, Strava will take the values the K2 provides, but you will also have the option of correcting elevation and distance in the Strava web app.
https://support.strava.com/hc/en-us/articles/115001294564-Elevation-on-Strava-FAQs
-
I'm glad it's not just me. I completely agree with Steve; the data should at least be consistent across the Hammerhead website. I also get that Hammerhead concentrates efforts on the head unit above the website and that would be fine except there are basic things that can only be done on the website - eg. create a route from an existing ride.
I've also found data is inconsistent when uploading to 3rd party websites - I don't use Strava, but upload mostly to Garmin and sometimes also to RideWithGPS. Attached are screenshots of one ride where climbing data is completely different across all 3 sites.
Distance data is correct, but it does make you wonder whether other metrics may have the same issue - heart rate, power etc. Not an issue for me, but how do the pros who use this kit get on with it??
Please sign in to leave a comment.
Comments
11 comments