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

Running Pace vs. Speed

I've got a Forerunner 305. I have it set to running and when I upload my run I have the choice of seeing pace or speed under the activity summary. If I go to the player to review the run my only choice is speed. I'd rather see pace. I can't seem to find a setting to make this possible. Anyone know?
  • Former Member
    0 Former Member over 14 years ago
    Well, I tried but I could not get the Player to do anything but mph. No Pace.
  • In my screens, anything w/ an activity type of running gives speed in min/mi and anything w/ an activity type of cycling gives mi/hr

    JP
  • Former Member
    0 Former Member over 14 years ago
    Just to confuse things further - the GC player uses the term Speed even when it is actually displaying min/km (min/mile) which is Pace. As far as I can see JP is right, running activities are min/mil or km and cycling are mi or km/hr.
  • Former Member
    0 Former Member over 14 years ago
    Speed charting bug in Garmin Connect Player

    during review with the Payer I see that a faster pace value is lower in the graph, eg. is closer to x axis, an a slower speed is higher, eg. farther from the x axis.
    I hope I'm being clear: a faster pace is shown in a lower position.
    values on the axis are upside down as well, they grow as they go farther from x axis. so value and graph are consistent, but, a faster pace means less minute per km...

    shouldn't it be shown the other way around?


    This has to be a known bug. We can only hope that it is fixed in the October 2010 update.
  • Graphing normally starts from 0 at the x-y intersection and increases numerically. The y-axis is min/km. As a result pace of 1min/km would of course be lower down the y-axis than 10 min/km.

    It's not a bug, it's the way graphs are generally drawn
  • Former Member
    0 Former Member over 14 years ago
    Graphing normally starts from 0 at the x-y intersection and increases numerically. The y-axis is min/km. As a result pace of 1min/km would of course be lower down the y-axis than 10 min/km.

    It's not a bug, it's the way graphs are generally drawn


    Yes, you are correct, it's not a bug and graphs are generally drawn with the smaller values lower than the higher values which creates a visual effect that most of us can immediately recognize

    BUT when graphing "pace" using the actual "pace value" the visual effect is upsidedown just like LILIUMDAVIDII said.

    It would be an easy fix if the pace was converted to mph and graphed as mph but labeled as pace (min/mile). Then the pace graph would give the correct visual effect.
  • Yes, you are correct, it's not a bug and graphs are generally drawn with the smaller values lower than the higher values which creates a visual effect that most of us can immediately recognize

    BUT when graphing "pace" using the actual "pace value" the visual effect is upsidedown just like LILIUMDAVIDII said.

    It would be an easy fix if the pace was converted to mph and graphed as mph but labeled as pace (min/mile). Then the pace graph would give the correct visual effect.


    A rabbit by any other name is still a rabbit. Just because you call it a cow doesn't change anything.

    Get used to what you are looking at. Either that or stand on your head :D
  • Former Member
    0 Former Member over 14 years ago
    A rabbit by any other name is still a rabbit. Just because you call it a cow doesn't change anything.

    Get used to what you are looking at. Either that or stand on your head :D


    You are missing the point of making a graph.

    Graphs are meant to convey a picture of the numerical data without standing on your head.

    A mph graph of rabbit speed vs cow speed would correctly show rabbits as faster.

    A pace graph using Garmin methods will incorrectly show rabbits as slower.

    If you expect us to use the graph upsidedown then tell Garmin to turn the labels over so we can read the data. :D