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

How to adjust values on graphs

Former Member
Former Member
When my runs are uploaded to Garmin Connect and then displayed on the various graphs, I find the graph scales too large. I can't see the trend across the plot very well. If I could expand the values then I could see the trends in my runs. Is there any way to expand these values so I can get better/bigger definition my results?
  • I would really like this feature also. The pace charts are almost useless visually if you stop at any point in the workout

  • Yes, simply click the double-arrow symbol top right on the graph to get the large view, and the you can use your mouse to select the area of interest, which will be then zoomed in

  • No, zoom function is totally useless, because it's doesn't scale Y-axis. If pace is up to 15:00, then after zoom it's still 15:00. Often pace is from 0:00 to 30:00 or 40:00 - then you only see a quite straight line. After "zoom" pace is even less readable then on full view.

    .

    Same thread with screenshots showing the problem:

    can-we-please-change-the-y-axis-scaling-on-garmin-connect-plots---elevation-pace-hr / 925700

    So auto scaling for charts it's just totally wrong on Connect.

  • No, zoom function is totally useless, because it's doesn't scale Y-axis.

    That's correct, of course, but already in the large view, you can see the curve and the values much better than on the small graph in the overview. And even very flat curves are quite well readable. I see no problem finding in them what I need. Can you show an example, where the large view is not sufficiently detailed? The ones on the link you posted look just fine to me.

  • The ones on the link you posted look just fine to me.

    Well, for me it's totally not fine - all I see is pace about 5:00. That's too much rounding. No need for graph if value is so rounded.

    Y-scale should be much smaller, to expose differences in pace.

    Adding that staying slow pace to Y-scale is just wrong.

    .

    Others examples would be quite the same, only line would be even more straight when Y-scale is larger, like 40:00.

  • Have to agree with BunBun here. Not a fan of he large Y scale. While the zoom does help (thanks for pointing that out trux), it's still not a great solution.

    But at least we have badges

  • Well, for me it's totally not fine - all I see is pace about 5:00. That's too much rounding. No need for graph if value is so rounded.

    You can move the mouse cursor to any point on the graph, and it shows you the exact time and pace in the tooltip, wherever you have doubts. 

    Customizable Y-axis would be certainly nice, but it is pretty well usable even without it.

  • Not a fan of he large Y scale.

    If you want to avoid the large Y-scale, warm up before and cool down after the measured activity (you can log them separately if you really need it). The Y scale is large, when, at some point, you run much slower than normally. When you keep your pace in some reasonabe range, the Y scale will be much better readable.

  • About pointing mouse on line I wrote that in linked post, but that's not convenient.

    Running all the time in similar pace doesn't guaranties smaller Y-scale. Sometimes pace changes for a second with no reason, on my run showed on the linked chart there was no stop. And again it's not convenient not be able to make stops, so that's bad workaround anyway.

    So yes, the best we can do here is to open chart in full view (but without zoom, as zoom is less readable), and then point mouse to see numbers.

    .

    But it would be really easy to scale charts properly, just cut not matching values, and on zoom re-scale Y-axis.

    So, for now the best workaround is to export activity and view it in some normal chart software when we want to properly analyze some training.

  • +1 to that BunBun!

    And staying within pace doesn't work for interval or rep sessions when you intentionally stop for rest... And these are the ones you really want to analyse too.

    I appreciate trux's enthusiasm in finding workarounds. But really Garmin needs to provide better charting options here.