search

ayoola-solomon / mytracks

Automatically exported from code.google.com/p/mytracks
0 stars 0 forks source link

Massively incorrect statistics #622

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
I experienced this issue twice in one day and then never again - my best guess 
is a timezone/date related issue.

The track appears to have been recorded correctly (as per attached CSV file - I 
have attached all of the other export formats as well, however I have not 
verified their contents), however the statistics are as listed below:

Name: 2011-10-31 07:50 To Work
Description:    
Date: 31/10/2011 7:50 AM    
Total Time: 0:33:52 
Moving Time: 266:42:25  
Distance: 174010.53 
Distance Unit: km   
Average Speed: 308213.87    
Average Moving Speed: 652.44    
Max Speed: 652.45   
Speed Unit: km/h    
Elevation Gain: 342 
Min Elevation: 3    
Max Elevation: 95   
Elevation Unit: m

In addition to the the map view shows a fully zoomed out map of the world, and 
no track is visible at any zoom level.

I am running MyTracks (v1.1.10 as of writing, it would have been the most up to 
date version at the time of the issue) on a SGSII running stock samsung build 
number GINGERBREAD.XWKF3 in Melbourne Australia, and the date was 31/10/2011. I 
was cycling to work, so these readings are very out of the ordinary!

Original issue reported on code.google.com by Chester....@gmail.com on 2 Nov 2011 at 11:29

Attachments:

GoogleCodeExporter commented 9 years ago 
Refer to issue 374

MyTracks is almost certainly including lat,lng 0,0 locations in the distance 
calculations. These could be probably checked for and logged or an error report 
emailed. The KML above contains multiple strings probably due to GPS lock being 
lost in the city high rise area  - how/where was the phone positioned while 
recording? Distance recorded is roughly 12 times to lat,lng 0,0.

Additionally issue 384 is also evident in the attached KML file.

Original comment by bigya...@gmail.com on 4 Nov 2011 at 1:18

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
I've seen this occasionally when the GPS gets confused and gives a location at 
some place a long way away. When it happens the GPS stays confused for a while 
and usually requires a reboot.

Original comment by kenep...@gmail.com on 19 Dec 2011 at 11:36

GoogleCodeExporter commented 9 years ago 
I've seen this issue too on several occasions.  The first time, the track 
looked correct on the map, but one point showed a 3,000 mile altitude change.  
The other two times, the maps and altitude looked correct (so did travel time) 
however distance shown is 10k miles.  One example is attached as a KML.  

Another point to note, the track appears complete- e.g there are no obvious 
gaps from GPS signal loss.

Original comment by tmnich...@gmail.com on 21 Mar 2012 at 9:45

Attachments:

GoogleCodeExporter commented 9 years ago 
In My Tracks 2.0.2, the statistics are now calculated from the saved locations, 
not from all received locations. As a consequence, invalid received locations 
are no longer saved and used to calculate stats.

Original comment by jshih@google.com on 10 Sep 2012 at 9:08