search

irfan-arshad-arbisoft / mytracks

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

Wrong distance recording #1412

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.every time when i record a track
2.
3.

What is the expected output? What do you see instead?
If I record a track, a too high total distance is displayed but in the map the 
recorded track looks good.
If I open KML file with Oruxmap, distance displayed is right.

What version of MyTracks are you using? On what version of Android? On what
phone?
MyTracks: 2.0.5
Device model: WIKO STAIRWAY
Firmware version: 4.2.1
Kernel version: 3.4.5

If possible please provide a log by uploading here.
Detailed instructions can be found here:
http://code.google.com/p/mytracks/wiki/HowToReportErrors

Please provide any additional information here:

Original issue reported on code.google.com by jacka...@gmail.com on 14 Oct 2013 at 11:36

Attachments:

GoogleCodeExporter commented 9 years ago 
Do you mean the total distance in the stats tab view is wrong?
Do you mind sharing a small sample track, as kml file? What is the expected 
distance? 

Thanks

Original comment by jshih@google.com on 13 Dec 2013 at 9:03

GoogleCodeExporter commented 9 years ago 
Yes I talked about stats tab wiew.
You will find enclosed kml files (MyTracks and Oruxmaps) and screenshots 
showing distance.
The right distance is given by Oruxmaps (see screenshots).
I didn't use MyTracks for 2 months and today when I exported and reimported kml 
file, stats tab view was ok (see screenshots)....

I will do a new test tomorrow using MyTracks, Oruxmaps and the speedometer of 
my car.

Thanks

Original comment by jacka...@gmail.com on 15 Dec 2013 at 7:49

Attachments:

GoogleCodeExporter commented 9 years ago 
Under Settings->Recording, check your settings for
- Recording distance interval
- GPS accuracy

When you reimport the data, it uses the current settings to filter out unwanted 
gps points. E.g., if GPS accuracy is set too high, it can easily accept gps 
points with large margin of error and causing the distance to be higher than 
expected.

Original comment by jshih@google.com on 23 Jan 2014 at 6:56

GoogleCodeExporter commented 9 years ago 
Same problem here. Distance and average speed on statistics page are 
approximately 10 times higher than real numbers. Recording distance interval is 
set to 10m (recommended) and GPS accuracy is set to 50m (also recommended 
value). 

I see same problem in OpenGPS tracker, related bug is discussed here: 
http://code.google.com/p/open-gpstracker/issues/detail?id=399. Probable the 
root of problem is a bug in android implementation of Location.distanceTo().

Original comment by nikolay...@gmail.com on 28 Jan 2014 at 8:53