Reported track distance way too far under poor GPS reception conditions

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Start track recording
2. Put phone into your pocket
3. Start running exercise
4. Finish running
5. Stop recording
6. Observe the "Total distance" numbers on the statistics screen.

What is the expected output? What do you see instead?
The "Total distance" numbers should be more accurate. The attached KML file 
gives a total distance of 8.83km where the real number is about 7.24km. A more 
reliable distance can be calculated by applying filter functions to the 
positioning data.

For example, opening the attached KML file in Google Earth gives a reading of 
8.03km so I guess this kind of functionality is already present there.

What version of MyTracks are you using? On what version of Android? On what
phone?
v1.1.1

Original issue reported on code.google.com by mikael.k...@gmail.com on 17 Feb 2011 at 1:08

Attachments:

• [2011-02-16 1006 (1).kml](https://storage.googleapis.com/google-code-attachments/mytracks/issue-340/comment-0/2011-02-16 1006 %281%29.kml)

[GoogleCodeExporter]

Original comment by rdama...@google.com on 30 Apr 2011 at 6:14

• Added labels: Component-Logic

[GoogleCodeExporter]

I believe the distance numbers it records are too far even under ideal 
conditions, so smoothing/filtering should always be applied.  I estimate it 
over records somewhere around 3%-5% for typical running speeds (7-9mph).

Original comment by jbierl...@gmail.com on 15 May 2011 at 4:18

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

See discussion in Google Groups - My Tracks - Differences Between Google Earth 
and My Tracks at 
http://groups.google.com/group/mytracks/browse_thread/thread/3db73dca27510742/8b
16769e0ec7696b#8b16769e0ec7696b

This was reported as fixed in issue 77 
http://code.google.com/p/mytracks/issues/detail?id=77&can=1&q=distance&colspec=I
D%20Type%20Component%20Status%20Priority%20Targeting%20Work%20Stars%20Owner%20Su
mmary

Original comment by kenep...@gmail.com on 5 Jun 2011 at 8:36

[GoogleCodeExporter]

Issue 507 has been merged into this issue.

Original comment by rdama...@google.com on 4 Jul 2011 at 1:30

[GoogleCodeExporter]

I'm having issues with this, too.  In my case, it seems to be related to its 
inability to pick up GPS signals.  I have other GPS apps on my phone and it 
takes at least twice as long to get signals good enough to get a fairly 
accurate pin on my location.  Sometimes, I can't get it to pick up a signal at 
all, even when the sky is clear and there are no trees or buildings in the way. 
 (using a Samsung Galaxy S)

Original comment by shorty0...@gmail.com on 29 Aug 2011 at 8:00

[GoogleCodeExporter]

As per jshih@, marking this as an Enhancement.

Thanks,

Original comment by nage...@google.com on 19 Nov 2011 at 12:39

• Changed state: Accepted
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Distances are now calculated from stored points, rather than using all gpx 
locations.

Original comment by jshih@google.com on 11 Sep 2012 at 1:04

• Changed state: Fixed