Race against self (previous track/time)

[GoogleCodeExporter]

Many people would like to be able to race against their previous times. While a 
stopwatch will allow this, adding GPS data allows racers to know whether they 
are ahead of, or behind their previous pace. 

Ideally, this would include one or more audio feedback paths. The first could 
just be pulsed tones. A higher tone would mean the racer is behind his/her 
previous time, with the tone being pulsed more frequently to indicate falling 
further and further behind. A lower tone would indicate being ahead.

The second path could be spoken feedback using TTS, "You are twenty seconds 
ahead of your previous time." or perhaps just "Twenty seconds ahead."

Additionally, after several times through a course, the user could also know if 
how he/she is performing in relation to his/her best time to that point so far, 
i.e. "You are five seconds ahead of your previous time, and three seconds 
behind your best time to this point."

I see this as mainly a training tool, and think most organized races would ban 
it, but for recreational use and training, I think it would add value. The 
shortcomings I can see would be the inaccuracies of GPS data. I would use this 
for mountain biking, and I move fast enough on wheels that 20 seconds 
difference may be less than the margin of error, especially under the wet 
northwest pines in Washington state.

Still, I'm very interested in seeing this work, and I'm interested to add this 
functionality myself, but would really appreciate someone's help as I go along. 

Thx,

D

Original issue reported on code.google.com by dblanch...@gmail.com on 11 Aug 2010 at 12:26

[GoogleCodeExporter]

If you are interested I have a patch that probably gets you 80% of the way 
there.  A long time ago another googler implemented most of the functionality 
but never finished the job.  Since then the code base has changed a bit so 
there would be some integration work needed but there is a solid bit of work to 
go off of.  Let me know if you are interested in the patch.

Original comment by sandordo...@google.com on 11 Aug 2010 at 12:35

[GoogleCodeExporter]

Man. That was a very long time ago. It should really be just a few days of 
work. If that patch is actually my old Cl I might consider finishing it up. 
Though it wouldn't happen until Oct.

Original comment by ejdehaye...@gmail.com on 11 Aug 2010 at 1:55

[GoogleCodeExporter]

I'd like to take a look at the patch, but Im' very new to both Java
and Android, still, I'm eager to learn and may be able to free up some
time next week.

Original comment by dblanch...@gmail.com on 13 Aug 2010 at 3:19

[GoogleCodeExporter]

Just pinging Sandor to post the patch :) Love to see other people contributing.

Original comment by rdama...@google.com on 25 Aug 2010 at 1:55

[GoogleCodeExporter]

Issue 72 has been merged into this issue.

Original comment by rdama...@google.com on 25 Aug 2010 at 2:26

[GoogleCodeExporter]

This is fine as far as it goes, but you might consider another use case while 
patching/ coding.

Instead of recording a new track, allow a user to follow an existing track 
(especially from import).  This almost brings the device to a point where you 
can upload a cue sheet and follow it (thinking Google Navigation for Bicycles). 
 Your cues would necessarily be limited to saying things like "you are 
off-course to the north" or purely visual, zoomed-in enough to anticipate the 
move.

Thoughts?

Original comment by christopher.wanko on 25 Aug 2010 at 3:24

[GoogleCodeExporter]

I thought I had added this before, sorry.

Original comment by sandordo...@google.com on 25 Aug 2010 at 5:22

Attachments:

• 10556265.pack

[GoogleCodeExporter]

Thanks!

(As a note to ejdehayedosar, that's a regular patch file generated from p4 pack 
- "patch -n 1 < 10556265.pack" should work)

Original comment by rdama...@google.com on 25 Aug 2010 at 5:31

[GoogleCodeExporter]

Original comment by sandordo...@google.com on 24 Sep 2010 at 11:30

• Added labels: Priority-Medium, Work-Large

[GoogleCodeExporter]

Issue 166 has been merged into this issue.

Original comment by sandordo...@google.com on 29 Sep 2010 at 5:18

[GoogleCodeExporter]

Progress/ status?

Original comment by christopher.wanko on 27 Oct 2010 at 5:29

[GoogleCodeExporter]

This sounds perfect; how can I apply this patch?

Original comment by sfgtur...@gmail.com on 4 Jan 2011 at 1:50

[GoogleCodeExporter]

The patch is include in comment 7.  It is far from straight forward to apply 
it.  It was based on a very different code base so it will take some work to 
get it running again.  If you have the time and knowledge I would love to see 
it included in a current my tracks revision.

Original comment by sandordo...@google.com on 4 Jan 2011 at 5:25

[GoogleCodeExporter]

I should mention that this is an extension of issue 15 (that one is just 
loading a second track, this one is also comparing the results).

Original comment by rdama...@google.com on 30 Apr 2011 at 5:37

[GoogleCodeExporter]

Issue 396 has been merged into this issue.

Original comment by jshih@google.com on 10 Sep 2012 at 11:25

[GoogleCodeExporter]

Something similar to what the strava (www.strava.com) would be ideal, along 
with the raw data being stored in Google drive.

Original comment by sfgtur...@gmail.com on 11 Sep 2012 at 1:37

[GoogleCodeExporter]

Issue 1308 has been merged into this issue.

Original comment by jshih@google.com on 10 Jun 2013 at 5:55