Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

altitude and altitude difference is differing on my Edge 1030 plus

PROFGRUEN
over 4 years ago

Dear all,

I detected during my last rides that my Edge 1030 Plus calculates the data field altitude difference not correctly:

on appx driven 100 altitude meters eg from 300 hm to 400 hm the data field altitude difference results in appx 5 hm more than the difference in altitude of starting and end point.

Has someone an idea how this inaccuracy in altitude difference measuring can be fixed?

Thank you in advance

ProfGruen

  • 0 over 3 years ago in reply to PROFGRUEN
    PROFGRUEN said:
    Question: if the barometer doesn't work precise - is it possible to change to a precise GPS based monitoring?

    GPS is worse. That's why the devices have a barometer.

  • 0 over 3 years ago in reply to dpawlyk

    I see - but I still have about 20% deviation at a 2 hrs tour with 30 km and apppx 1000 altitude gain meters ...

    Do I make something wrong?

  • 0 over 3 years ago in reply to PROFGRUEN

    Which number is right?

    Your 30 km ride probably has ups-and-downs. The estimated elevation is based on DEM (elevation data) and that's often an underestimate.

    It's an estimate. It's poor measure of effort because it doesn't account for grade.

  • 0 over 3 years ago in reply to dpawlyk

    Hi dpawlyk,

    unfortunately I am not an expert like most of you with these things. I detected the difference on my usual rides when the reported altitude gain did not match with the altitude gain I received when inserting the same route in BaseCamp.

    Therefore I  went up a long hill without up and down and even then I has the appx 20 % deviation (that is Edge 1030 Plus shows appx 20% more driven altitude gain).

    Despite I do not understand why the Edge 1030 plus cannot consider and measure altitude gains including ups an downs ( eg 100 alt meters up, then 20 down and 30 up - why is it not possible to properly add 100+30 ...?) - why is the Edge 1030 Plus not even capable to measure a straight ascent properly? I start at 300 altitude meter, ascend to 600 altitude meter straight up - and receive appx 360 altitude meter gain).

    Thank you in advance

    ProfGruen

  • 0 over 3 years ago in reply to PROFGRUEN

    ähem: this sentence I did not catch (sorry Austrian ;-)): It's poor measure of effort because it doesn't account for grade.

  • 0 over 3 years ago in reply to PROFGRUEN
    PROFGRUEN said:
    I detected the difference on my usual rides when the reported altitude gain did not match with the altitude gain I received when inserting the same route in BaseCamp

    Yes, you have two numbers. Which one is correct? It seems you are seeing the BaseCamp number as the correct number but that's an estimate too.

    PROFGRUEN said:
    Therefore I  went up a long hill without up and down and even then I has the appx 20 % deviation (that is Edge 1030 Plus shows appx 20% more driven altitude gain).

    This should certainly be a simple case to measure. I don't have enough information to figure out what might have happened in this case, Anyway, knowing the expected number (and where it came from) and the number you got is useful information. "20% deviation" isn't enough (it's useful to know if it's higher or lower).

    PROFGRUEN said:
    I start at 300 altitude meter, ascend to 600 altitude meter straight up - and receive appx 360 altitude meter gain).

    Over what distance? The devices should be more accurate if it's a large gain in a shorter distance.

    People seem to expect a higher degree of accuracy than appears to be obtainable in the real world.

    =============

    Note that one can get odd estimates from the DEM data.

    For the following the gain is really about zero but the estimate is 56 meters. The DEM data doesn't account for the road being on a bridge.

    ridewithgps.com/.../37834782