Open GoogleCodeExporter opened 9 years ago
I would greatly appreciate this addition.
Original comment by jerm...@gmail.com
on 13 Jul 2010 at 6:47
Ditto. This would be really useful. Or, an option to make the 'average speed'
announcement only for the last interval. Unless I've misunderstood it, it
appears to announce the average for the whole activity.
Thanks,
Tom
Original comment by thomas.h...@gmail.com
on 1 Sep 2010 at 3:30
Thinking about this, you'd need to set an interval over which the pace is
calculated as the instantaneous speed is very spiky
-- see
http://code.google.com/p/mytracks/issues/detail?id=115
Add smoothing option for speed
Original comment by thomas.h...@gmail.com
on 1 Sep 2010 at 3:31
Original comment by sandordo...@google.com
on 24 Sep 2010 at 11:26
Issue 219 has been merged into this issue.
Original comment by sandordo...@google.com
on 16 Nov 2010 at 10:52
this would be a great feature... do u need more developer help?
Original comment by jcots...@gmail.com
on 11 Dec 2010 at 4:55
We can always use more help. This is all done by volunteers and 20% time.
Original comment by sandordo...@google.com
on 12 Dec 2010 at 1:51
Original comment by sandordo...@google.com
on 17 Feb 2011 at 5:51
Original comment by rdama...@google.com
on 30 Apr 2011 at 6:08
Being able to compare current pace to only the last X minutes would let me know
which way I am trending. Ideally, for hiking, I would like to compare the last
5 minutes to the previous 15 minutes. This lets me compare my pace as the
hiking terrain changes instead of the entire duration.
In addition to pace, plz consider allowing heart rate as a trending comparison
measurement. I do not have the current model that works with My Tracks but am
curious if heart rate data is included in the audio announcement.
I had a heart rate monitor that beeped if my heart rate got too high/low for a
targeted range. This range was based on some basic profile data (age, sex,...)
and it determined an ideal exercise min/max heart rate range. If heart rate was
included in the elevation/pace graph, the line could indicate 'in range' and
'out of range' by color/line style.
Original comment by bradsmit...@gmail.com
on 8 May 2011 at 10:32
I would also appreciate the addition of audible heart rate feedback. While the
addition of zone feedback would be helpful from a training standpoint, the
user's current heart rate or moving average from some short interval could be
added to the verbal feedback. This would help users keep their heart rate in
an acceptable range and go hand in hand with the pace update feature. The goal
being to promote safe, but effective exercise.
Thanks
Original comment by SimeonEi...@gmail.com
on 30 Apr 2012 at 9:06
Issue 1020 has been merged into this issue.
Original comment by jshih@google.com
on 10 Sep 2012 at 10:46
Issue 1186 has been merged into this issue.
Original comment by jshih@google.com
on 10 Nov 2012 at 6:32
Target pace (and optionally, heart rate) is missing from all other apps too.
This would be a killer feature for MyTracks!
Original comment by ulf...@gmail.com
on 25 Aug 2013 at 6:16
The interval training is a must to improve stats. Runtastic has implemented a
nice interface for interval training. You can add blocks of one of the selected
pace range(slow,med,high) for a amount of time or distance.
Original comment by yan.lant...@gmail.com
on 29 Aug 2013 at 1:33
It would also be a nice feature providing the "actual speed/pace" (e.g. the
pace resulting from the last N coordinates) in the lock-screen widget
(independently from the warning). This would allow users monitoring the actual
speed/pace without efforts.
Original comment by lorenzo....@gmail.com
on 31 Jan 2014 at 1:57
Issue 371 has been merged into this issue.
Original comment by jshih@google.com
on 14 Oct 2014 at 8:58
I would love to hear average speed over last km (not just average since
starting) in the audible info. Looking at the dates on this thread, have I
missed this as a feature or are there not many people wanting it? Thanks,
Original comment by tomoakle...@gmail.com
on 17 May 2015 at 9:45
Original issue reported on code.google.com by
dkh...@gmail.com
on 8 Jun 2010 at 7:58