Runtastic's Elevation Info...I don't understand it! Duh!

Options
So_Much_Fab
So_Much_Fab Posts: 1,146 Member
edited January 22 in Chit-Chat
I consider myself to be pretty smart but for the life of me I can't understand how to decipher Runtastic's elevation summary info. Derp.

Case in point, from today's 5k:

runtasticxxxx.jpg

- For the life of me, I can't understand the graph on the top.
- In the area highlighted on the bottom, what does "up" 19 ft. "down" 26 ft. mean?

Apparently, I need to go back to school, or something. :laugh:

Replies

  • bluefox9er
    bluefox9er Posts: 2,917 Member
    I think you are bloody smart to figure out how to add your comments in red on the picture. as a semi pro photographer, my photoshop skills don't go that far.
  • So_Much_Fab
    So_Much_Fab Posts: 1,146 Member
    Bumping because I still want to know.
  • thekyleo
    thekyleo Posts: 632 Member
    It looks like the top graph is your speed in relation to the distance you traveled as well as the elevation change. The elevation change can be due to the course itself and may not necessarily be correct.
  • BerryH
    BerryH Posts: 4,698 Member
    It's how many feet you are above sea level as you go up and down hills or slopes on your run. So your first couple of miles were flat, but in your last mile you went up 19 feet during the course of that mile and down 26 feet. So with you ended up somewhere 8 feet downhill of where you started or (more likely) the GPS isn't 100% accurate.
  • pdworkman
    pdworkman Posts: 1,342 Member
    But take a look at the topo map at the top. It was not a flat run for mile 1 and 2. And mile 3 was roughly a net 0 from the starting elevation. I can't reconcile the two, even laying a grid over the graph to count the gain/loss.
    It's how many feet you are above sea level as you go up and down hills or slopes on your run. So your first couple of miles were flat, but in your last mile you went up 19 feet during the course of that mile and down 26 feet. So with you ended up somewhere 8 feet downhill of where you started or (more likely) the GPS isn't 100% accurate.
This discussion has been closed.