It would be extremely nice to be able to configure the y-scale on charts for any given workout. I have an activity where I gained ~100ft elevation and lost about the same, yet it looks like a straight line because it is scaled 0-1200ft.
"very easy bugs" or what we consider a bug can take eternity for large companies like Garmin to fix or change. When I worked in the IT world, we consulted to some very large international companies. Some had a very large bureaucracy of management to go through for along with all the QA testing that had to be performed and training to make sure the QA people in fact knew what they were supposed to test for much less how to use the product. This process literally took years for a simple change to be approved. And by that time in many cases, the platforms the tested product ran on would be out of support and the process would again have to be restarted.
You'd really be surprised at the names of companies this occurred at. However I can't in good conscience divulge that information.
And now you're a Garmin employee? Of course they could have fixed this long time ago if they had cared, obviously they don't. I know exactly how q&a works and what time you could expect it to take. Stop defending them, please.
It would be extremely nice to be able to configure the y-scale on charts for any given workout. I have an activity where I gained ~100ft elevation and lost about the same, yet it looks like a straight line because it is scaled 0-1200ft.
Improve 310X software graphics by letting user adjust the base-liine. For example a display of hiking at a 1500m altitude is useless because changes of 10 m are just liittle ripples. All you nee to do is let the user subtract an appropriate number from the altitude before plotting , It should be easy to do. Also I think you should restore the option for two data strings on one plot Heart and Elevation say.
Just because I had to tie my shoe during a run the pace graph becomes useless. There seems to be one pixel difference bewetten a 5:30 min/km and a 6:00 min/km pace.
Add me in. The elevation scaling was useful but in the last month jumped to such a large scale that I flatlines unless you're climbing mountains. If you can't let us choose scaling then let the autoscale read the highs and lows and adjust itself. Even Excel can do that!!
Well, to read the hight and lows would not suffice. For PACE (this is the graph i would like to improve most) the hight reaeches infinity if you stop at a light are tying your laces. At the moment it goes up to 20 min/km which is not at all practical ... this is slower than crawling speed. I think it is almost impossible to run slower than 8 min/km. Maybe up a hill you get as slow as this but not evere to 20 min/km. To be able to set this to 10 min/km for example would be great.
+1. Add me to this. The pace chart is utterly worthless. Training center has terrific graphing, and that is a very old program. We have invested money in high end Garmin equipment(I love my Forerunner 620), but what a pity to not be able to visualize a simple pace chart. I ran 7mi at 7min/mi pace today, with fast closing miles, yet my pace chart is a flat line with one massive dip to 60min pace, when I stopped to say hello to a friend.
Thank you Please fix this simple issue on Garmin Connect and GC Mobile.
I find it odd that the graphs' scale cannot be changed. I'm a runner, and the area I'm running barely goes between 50 to 100 feet, but the elevation scale displays from -600 to 600. I would think the scale would be user changeable. Runkeeper doesn't have changeable scale but it at least generates a scale fitting the lows and highs of a graph.
So three years passed and nothing has been done about this since the 1st post..
I've had it with Garmin, coming from Suunto which has this and also many other competitors I'm at a loss why Garmin can ignore user requests yet stay in business. All the graph scaling needs to be dynamic, even the phone app scaling is better. (and the fact no full screen view for the map) ....
