Related
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

CAN WE PLEASE Change the Y-Axis scaling on Garmin Connect plots? - Elevation/Pace/HR

Sean
over 8 years ago
I have been searching through posts dating back to 2012 requesting the ability to change the y-axis on the Elevation/Pace/HR etc plots in garmin connect. Plots look fine on the app but on PC the dynamic range is very large giving the data no meaning (basically a flat line). The elevation especially is completely useless.

Its seems like a very straight-forward request and standard functionality of most plotting software. It would improve end-user satisfaction immensely, ideally a scroll bar or direct number input for the y-axis numbers.

Alternatively, an explanation of why it may not be a easy as it appears would be helpful (no time/resources etc).

Thanks for any response!


  • 0 over 5 years ago in reply to BunBun!

    It takes some determination and a lot of patience to get through via email, but Garmin has fixed some of the bugs I have reported.  Make sure you get a case number so that the engineers do investigate.

    Garmin only monitors a small number of the forums so writing here is no guarantee that Garmin will act.  If everyone who has +1ed on this post emails Garmin they might do something though.

  • 0 over 3 years ago
    When I get back home after a run, the Pace graph is one of the first things I look at. Problem is....if my pace has varied significantly over the run (say, if I've stopped for a few seconds at the traffic lights), then the 'y' axis of the pace graph becomes too big to allow useful analysis of the actual pace whilst running.

    My Pace graphs show a 'y' axis right from 30 minutes per mile up to 6 minutes per mile....not very useful.

    Could Garmin Connect 'trim' out the stopped sections, or allow 'zoom' into the pace graphs to help me?

    Cheers!
  • 0 over 3 years ago in reply to JimHarbidge

    they should use a logaritmic scale in the Y, so the closer to 0 (faster) the more zoomed would it be) Indeed 15 sec/km diffeernce are a lot when you run ar 4':00"/km, but are nothing when you hike at 25':00"/km

  • 0 over 2 years ago

    +9357 This is by far the biggest flaw in Garmin Connect - and has been for ever!

    Should be easy to fix: Make the user enter a threshold value that should be the lowest pace on the y-axis, and scale between this value and the max-pace value. Min-pace value can be stored in user profile.

  • 0 over 2 years ago

    Analyze data and get 95% of data points in Y-Axis. We need to ignore those fallouts when you've stopped at a traffic light and restart. Or, just have Garmin assume the same pace from before the stop for the first 15 seconds until it re-establishes speeds. I can't believe the Garmin decisionmakers think these graphs are useful. Maybe all of them run and never stop mid-run! Please, after this many years, add the data field to let us enter a high/low Y-axis and let HighCharts re-calculate the graph. I'm about to send these pages to my own HighCharts engineers and ask them for help!

  • 0 over 2 years ago in reply to MikeL
    MikeL said:
    Analyze data and get 95% of data points in Y-Axis. We need to ignore those fallouts when you've stopped at a traffic light and restart.

    Not a bad idea, but it doesn't cover the case when you run intervals and you have significant periods of standing or jogging rest time.

    I actually like how both Strava and the Garmin Connect mobile app (not website) handle this -- they just have an arbitrary minimum pace on the y-axis like 11:00/k. The Garmin Connect website kinda does the same thing, except their arbitrary minimum is arguably chosen more poorly (40:00/k).

    123none123 said:
    they should use a logaritmic scale in the Y, so the closer to 0 (faster) the more zoomed would it be) Indeed 15 sec/km diffeernce are a lot when you run ar 4':00"/km, but are nothing when you hike at 25':00"/km

    Runalyze does this and I agree it would be the best solution, but I don't think it would make sense to non-technical users.