Forums >Suggestions and Feature Requests>Calculate grade
Good Bad & The Monkey
I'm running somewhere tomorrow. It's going to be beautiful. I can't wait.
Poor baby
Interesting. Why does your version of the motionbased come up with 2496 feet of elevation change each way, while the motionbased run profile you linked to has over 4000? FWIW, this is my motionbased profile from Monkey 2007 - http://trail.motionbased.com/trail/activity/4468919 RA may ultimately have elevation data more frequently than every 200 m.
...As I see it, the question is this : is it accurate to calculate overall elevation change by including every 1-2 foot rise and fall in the road?...
Why is it sideways?
Don't let Trent fool you. On average, the course is flat as a pancake.
Kick that Halfer down!!!
In terms of elevation data resolution, the motionbased Gravity Service uses USGS reference elevation derived from a true altimeter to replace the GPS elevation estimates, the same as mapmyrun and runningahead. It is as accurate as we have. It does the replaces based on the recorded Lat and Long data, which as accuracy to ~98%+. It should be pretty good, even at every 3-10 second sampling.
Sampling frequency consistency is not necessarily an equalizer. A flat course like Chicago, or one with a steady consistent grade, like Grandfather Mountain, would give the same estimates whether the sampling were done every 0.1 mile or every 0.01 mile. A rolling course, by contrast, would have its elevation estimate trimmed down by sampling that is too infrequent. I think the goal is not necessarily to be consistent so much as to be true; make sure that every change in contour is captured.