search

CompanyGateways / mytracks

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

Ignore points that are very far off track. #374

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Hard to tell. I used the app only twice and got this issue once.
2.
3.

What is the expected output? What do you see instead?
You need to make sure you are ignoring such impossible points. Please add some 
smoothing algorithm.

What version of MyTracks are you using? On what version of Android? On what
phone?
I use version 1.1.2 on Samsung Galaxy S running Android 2.2.

If possible please provide a log.  Either upload here or send to mytracks-
support@google.com.
Detailed instructions can be found here:
http://code.google.com/p/mytracks/wiki/HowToReportErrors

Log sent from my gmail account - amitshofar@gamil.com.

Please provide any additional information here:

Original issue reported on code.google.com by amitsho...@gmail.com on 2 Mar 2011 at 2:33

GoogleCodeExporter commented 9 years ago 
This comes up periodically.  I renamed the issue to reflect what it would take 
for my tracks to keep working.

Original comment by sandordo...@google.com on 2 Mar 2011 at 3:25

GoogleCodeExporter commented 9 years ago 
I occasionally have this problem.  It's very annoying because one aberrant 
point makes the data from the whole track pretty useless.

Original comment by dpg...@gmail.com on 18 Jul 2011 at 11:42

GoogleCodeExporter commented 9 years ago 
Issue 537 has been merged into this issue.

Original comment by rdama...@google.com on 8 Aug 2011 at 7:17

GoogleCodeExporter commented 9 years ago 
Issue 521 has been merged into this issue.

Original comment by sandordo...@google.com on 11 Aug 2011 at 5:00

GoogleCodeExporter commented 9 years ago 
I don't see a comment I emailed in, but I exported the My Tracks file to the 
Garmin MapSource program, along with a track I made with my Garmin GPS60csx at 
the same time as the My Tracks recording.  The tracks were virtually identical 
with no apparent outliers.  Since the difference between the two recordings was 
about .25 miles in 1.75 miles with about 500 points or so, it wouldn't take 
much of a distance calculation error, such as a round off error, when 
calculating the distance between each point and adding them up (if that's how 
its done). Or it could just be inaccuracy with the phone GPS hardware compared 
with the Garmin GPS.  The error would be about 2.6 feet per interval.

Original comment by drjud...@gmail.com on 11 Aug 2011 at 5:52

GoogleCodeExporter commented 9 years ago 

Sorry for the cross post in issue 571. Using the kml downloaded from the map 
links in issue 521 - that is :

correct:
http://maps.google.nl/maps/ms?msid=206033647420482726903.0004acc526b9ee6837c80&m
sa=0
incorrect:
http://maps.google.nl/maps/ms?msid=206033647420482726903.0004acc4fbc648f79b814&m
sa=0
incorrect:
http://maps.google.nl/maps/ms?msid=206033647420482726903.0004acc4face791e455aa&m
sa=0

1) the track section dated 2011-09-12 22:05 (part3) has only two points, both 
of which are lat,lng 0,0  ie in the Gulf of Guinea. So something initialised 
but not set with data?

2) the track dated 2011-09-12 10:41 (part3) shows a distance of 11670 km. This 
is exactly the distance from the start point location to location lat,lng 0,0 
and back to the start location again; within a couple of km). I checked the kml 
file, however I found no lat,lng of 0,0 in any of the track sections. But this 
still roughly matches up with the problem identified in 1) above. This can be 
checked by loading the kml/gpx file into Google Earth and measuring from the 
start point to lat,lng 0,0

3) Re When multiple track sections are in use: why is there no (part 0) or 
(part 1) labels? The part numbering always starts at part 2.

By the way I dream of being able to ride on bike tracks like those seen on that 
route  :-))

Original comment by bigya...@gmail.com on 13 Sep 2011 at 11:01

GoogleCodeExporter commented 9 years ago 
If a bicycle wheel sensor is available, some sanity checking of the GPS 
readings would be possible. When riding on straight lines, you could 
auto-calibrate the wheel size, like the Garmin Edge series does.

If the device also has an electronic compass, you might be able to use it 
together with the wheel sensor as a "poor man's GPS" in long tunnels and other 
areas with poor GPS coverage.

Original comment by msmak...@gmail.com on 3 Dec 2011 at 9:17

GoogleCodeExporter commented 9 years ago 
Hey,
Yesterday was cycling and I had the same issue. All of a sudden, the stats 
changed to ridiculous values.
It it's the second time this is happening to me. It's there a way or a fix to 
this issue?

File attached below as gpx

Regards,
Dorian

Original comment by xuer...@gmail.com on 25 Mar 2012 at 11:50

GoogleCodeExporter commented 9 years ago 
Attaching file now. Sorry.

Dorian

Original comment by xuer...@gmail.com on 25 Mar 2012 at 11:54

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
This is a link to the map. 
https://maps.google.com/maps/ms?msa=0&msid=206757088112217671680.0004bc004eea7c8
1eccc8

Don't know why gpx file not loading...

Dorian

Original comment by xuer...@gmail.com on 25 Mar 2012 at 12:30

GoogleCodeExporter commented 9 years ago

Original comment by jshih@google.com on 13 Oct 2014 at 9:54