View Single Post
Old 07-05-16 | 10:04 AM
  #4  
deapee's Avatar
deapee
Ride On!
 
Joined: Apr 2016
Posts: 970
Likes: 3

Bikes: Allez DSW SL Sprint | Fuji Cross

Originally Posted by morningskies
On the surface this seems like a simple question. With percent gradient being a simple calculation of rise/run *100% (or more precisely tangent of the slope angle *100%).
You realize that n * 100% = n right?

That being said...Strava operates on many different data points including topographical data and data sets supplied by various riders with an altimeter. The altimeter data, I would assume, is manually inspected and only on an area of concern. Say a very popular segment that is literally ridden by hundreds of riders and say 10-20 people flag the elevation data there -- a person may look at the data gathered for the segment and alter the elevation correction data. Let's be honest, topographical maps are not very accurate for a newly paved bike path, for example, but may be accurate enough when determining how much higher above sea-level a town is than the nearby river and/or drainage system.

That also being said, it is a very simple question.

Divide the rise by the run. Multiply this number by 100 (not 100%) and you have the percentage slope.

You can't change that calculation ... your question is related to where Strava obtains their data points -- which is a question for them specifically...because no one is going to answer that but them for a specific location.
deapee is offline  
Reply