So why does Strava…

[KelOnWheels]

… think my biggest climb is 21 feet from last June?

Topic

[DismalScientist]

Somewhere in the depths of Strava software they thought a “climb” near the airport on the MVT was 400 ft or so. Although the elevation has be corrected, it still shows on many accounts as the biggest climb. The only way to fix this is riding up this a few times: http://www.strava.com/segments/609651

[ShawnoftheDread]

@DismalScientist 60587 wrote:

Somewhere in the depths of Strava software they thought a “climb” near the airport on the MVT was 400 ft or so. Although the elevation has be corrected, it still shows on many accounts as the biggest climb. The only way to fix this is riding up this a few times: http://www.strava.com/segments/609651

Alternatively, the lazy/non-abnormal could open a service ticket with Strava and they’ll reset it for you.

[vvill]

@KelOnWheels 60580 wrote:

… think my biggest climb is 21 feet from last June?

Strava will tell you it’s because you need to Upgrade to Premium.

[Bilsko]

@DismalScientist 60587 wrote:

Somewhere in the depths of Strava software they thought a “climb” near the airport on the MVT was 400 ft or so. Although the elevation has be corrected, it still shows on many accounts as the biggest climb. The only way to fix this is riding up this a few times: http://www.strava.com/segments/609651

Yeah, Strava can’t handle bridge elevations (ever look at the elevation when you cross Key Bridge and see the big dip on one side and climb on the other? It thinks you rode right through the Potomac)

I had one instance where it had me ride 500+ feet from the Georgetown Waterfront up onto the Whitehurst Fwy in a distance of 100 ft or so. It appears they scrubbed that segment/climb.

Veloviewer should help you pinpoit data errors.

[Hancockbs]

@Bilsko 60608 wrote:

Yeah, Strava can’t handle bridge elevations (ever look at the elevation when you cross Key Bridge and see the big dip on one side and climb on the other? It thinks you rode right through the Potomac)

It never occurred to me that this is one of the differences between my Garmin recorded elevation and the elevation that shows up on various mapping programs, but it makes perfect sense. Thanks for pointing it out!

[KelOnWheels]

@ShawnoftheDread 60595 wrote:

Alternatively, the lazy/non-abnormal could open a service ticket with Strava and they’ll reset it for you.

Yep, that’s what I did. Apparently not an uncommon problem.

[Author]

Replies