If there is a discrepancy between two recorded values one must be more correct than the other. It makes sense that Garmin Connect would have the ability to correct for such errors.
For example: after my run tonight my average and average moving pace both were lower than my fastest pace. That can't be right. By any definition of "average" I'm aware of it is a value that lies between max/min measurement. Since this is the case, one would think that the software would automatically correct for such inaccuracies.
In addition, today I ran over the 59th street / Queensboro bridge in New York. According to my 405 I had DEscended over 60 feet by the time I reached the height of the bridge!!!
(it actually went from +96ft to -30ft to +20ft (peak), then after I was down from the bridge I had lost 3ft from the peak and thus ended up on +17ft)
I know the elevation data won't be 100% accurate, but such a grave error makes the data completely useless. It's one thing to have the data have a slight margin of error, but in the right direction at least, and another when it registers elevation loss when you've climbed a bridge.
Surely there must be a way for the software to interact with Google maps which contains terrain data and thereby correct it, or?
