[Idea] Fixing elevation data for Climber/Dashboard map

Follow

Fernando

• January 02, 2024 21:20
• Edited

Hi all, well, this is a known issue that depends of map elevation source, not directly from HH... Map elevation data is not accurate in many segments, and we observe weird things in Climber from time to time, like having a 22% inclination advised on Climber at a point when you know all the segment is not more than 3% (real case at a segment I ride regularly).

But I was wondering if it could be possible a reasonable post-adjust to the principal elevation source... I will explain the idea. Bear in mind that I'm not an expert, and don't know the system from inside, so I don't really know the implementing problems that it could have. Apologises for this 🙏

Maybe most of the Karoo users are an incredible army of helpful people that wanted to give a hand to improve the whole HH user system: Dashboard + Karoo. All of these karoo users have an incredible weapon to measure the elevations, our own karoos and their internal sensors, barometer, gps, etc. Every route we do, all elevation data are stored in our rides.

The idea will consist on picking all that data (if user obviously gives permission to HH), to help HH to partially correct the elevation problems, if many of karoos ride the same segment, it is possible to have an enough sample to make a better average approximation to the real elevation of the segment, rather than the map source offers. Having a minimum of different units measuring the same will also reduce the other known issue that several units has with bad elevation readings. Users that have that problem can be ineligible for this purpose.

It also could be possible to have this feature with a configuration switch, in order users can activate the map elevation correction based on other users records or not.

As I said, I'm not an expert, but I can understand that it could imply lots of calculations, and maybe having an alternative map to store the modified elevations (corrected by karoo recollected data). But it is only a very high level idea. Your engineers will know how can approach the problem better than me, and if it is something affordable in your actual conditions. Also, maybe HH could make an alliance with the map elevation provider to share data and improve also the map source with the karoos measurements... 🙄

Anyway, I hope you can solve this matter in a future, many people will be pleased. Thanks for your effort!

Best regards.

1

• 

  Jim C

  • January 02, 2024 23:14

  Good idea but a key spanner in the plan is assuming our "karoos and their internal sensors, barometer, gps, etc" are accurate and it's only the elevation source which is corrupt. Last weekend my offroad route was calculated at 3,500m climbing instead of 368m 🤷‍♂️

  0

  Comment actions Permalink
• 

  Fernando

  • January 03, 2024 12:39

  Hi Jim, I'm assuming on my post that there are a bunch of karoo units that have a problem with registering the elevation (this is another known problem without any solution yet, it could be a hardware issue), obviously these units cannot be used for this purpose. Sorry about yours 😟 ... though, seeing that I climbed 3500 m would me feel very good after a ride 😂 (just joking, but maybe you can contact HH Support to ask for another karoo unit for replacing yours, I know people who had the same problem and did it successfully)

  Also I think that the idea I exposed could be very limited, because ideally assuming that HH implements it, it only will correct the segments with huge cyclists traffic, and also assuming that a minimum % of these cyclists use karoo, to get the significant records to make the elevation corrections. As I said it is only an idea, and it's free 🙂

  Regards.

  0

  Comment actions Permalink

Please sign in to leave a comment.