Originally Posted by at.rex
...my bike computer with altimeter and also a Garmin CS60 GPS unit. On the first part of the ride I went 12.5 miles and climbed a total of 711 feet according to the two units. GPSLogger recorded 1070 feet. On the second part of the ride I went 18 miles and climbed a total of 1106 feet according to the two units. GPSLogger recorded 1711 feet.
It's difficult for me to express what I wanted to say - I don't doubt, that the results GPSLogger currently reports are not the values you expect...
Ride 1: 12.5 miles and climbed a total of 711 feet
Ride 2: 18 miles and climbed a total of 1106 feet
Is the first one you send me? [or are you now talking about different ride again?] I am sorry I am a bit confused
... What I wanted to say with my '500ft' post question was, that I have already locally adjusted the GPSLogger code - and with that adjustment the dialogue say: gained 552feet.
I agree, that 522ft does not equal 711ft... It's quite difficult to find a good/reasonable algorithm that reflects:
a) GPS data accuracy failures (deviation)
b) Logging interval
Concerning the 1000 point example I have given view posts above - with the Old Code we would had get 500m gained - with the new implementation we would had get more or less 0m gained... so IMHO it's getting closer...
So what I am asking you is for "good" additional ideas/algorithms that could by allied.