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

Elevation Corrections - Bridges

Former Member over 12 years ago

I run across the George Washington Bridge that spans NY and NJ. When I upload the workout data from my 610 to Garmin Connect, if "Elevation Corrections" is enabled it ignores the bridge and the elevation graph plots a path goes straight down beneath the Hudson river and back up the other side.

Is this issue common to bridges? Given that my activity type is "Running" it would be nice if the software could determine that I have crossed the Hudson using the bridge.

At the moment, the "Elevation Corrections" feature leads to wildly inaccurate data so I disable it and rely on what I've captured with the device.

Mike

0 cdmackay over 12 years ago

Yup, this is just how it is.

With EC on, you're relying on the geo dataset(s) Garmin are using to relate a GPS location to an elevation. People have noted that these sometimes are precise enough to "do the right thing" for large bridges, but in general, they're going to show the ground elevation under the bridge.

With EC off, you're going to get the device's view of elevation, which will be either GPS, barometric, or some clever fudging of the two. GPS alone can be tens of metres out, and barometric requires regular re-calibration (or the GPS-based fudging); again, all this can produce unreliable results.

0 Former Member over 12 years ago

ok, thanks for the quick response.