search

CompanyGateways / mytracks

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

previously recorded tracks drawn with reduced accuracy after installing v1.1.5 RC1 #447

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Look at some previously recorded tracks from old version of MyTracks 
(v1.0.21 for example). Note how accurate the drawn track is (look at areas 
where the track curves or changes direction).
2. Upgrade to v 1.1.5 RC1, look at the same previously recorded track.
3. Note how the track will be drawn with less accuracy (lots of straight lines 
cutting through what had previously been properly displayed curves).

What is the expected output? What do you see instead?
Expect to see the same level of accuracy on the displayed track after upgrade. 
Instead, the track is drawn with less accuracy, perhaps using less points, so 
now many longer straight lines are displayed cutting through areas where the 
track was actually recorded. 

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

v1.1.5RC1, on HTC EVO (running Cyanogen mod 7._, Android 2.3.4).

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

Please provide any additional information here:
Please note - this is not an issue of GPS accuracy and the recording of new 
tracks. This is an issue of how the same tracks are being drawn/displayed in 
the new version vs. an old version.

Original issue reported on code.google.com by galt...@gmail.com on 7 May 2011 at 10:29

GoogleCodeExporter commented 9 years ago 
Would you be so kind as to send me either a My Tracks backup file or an 
exported GPX track with which you see this effect? I made a few attempts with 
my own tracks but saw no noticeable differences between the two versions.

Original comment by rdama...@google.com on 9 May 2011 at 9:31

GoogleCodeExporter commented 9 years ago 
Here's a link to a gpx file of a track : http://db.tt/dtkamca

Original comment by galt...@gmail.com on 9 May 2011 at 9:40

GoogleCodeExporter commented 9 years ago 
If that doesn't show what I've described I will take some screenshots. Also, 
the map that is uploaded to Google Maps displays thethe expected level of 
accuracy.

Original comment by galt...@gmail.com on 9 May 2011 at 9:42

GoogleCodeExporter commented 9 years ago 
Screenshots attached.

Original comment by galt...@gmail.com on 9 May 2011 at 10:12

Attachments:

GoogleCodeExporter commented 9 years ago 
While I haven't been able to reproduce this one yet, I did find a drawing bug 
today which I still need to investigate (it would connect some point in the 
track to the starting point).

Original comment by rdama...@google.com on 10 May 2011 at 1:52

GoogleCodeExporter commented 9 years ago 
If there's anything more I can do to help identify or demonstrate this issue, 
I'd be happy to follow any suggestions.

Original comment by galt...@gmail.com on 12 May 2011 at 5:15

GoogleCodeExporter commented 9 years ago 
Btw, I'm thinking that the GPX export may not have been enough for whatever 
reason - when I import it I simply don't get the same result as you're getting. 
Would you mind sending a backup file to me? (send it to my e-mail if you don't 
want to share it publicly)

Original comment by rdama...@google.com on 17 May 2011 at 1:26

GoogleCodeExporter commented 9 years ago 
Sure, although I don't know what your email is. I'm guessing it's is not 
<rdama...@google.com>.

Original comment by galt...@gmail.com on 17 May 2011 at 1:43

GoogleCodeExporter commented 9 years ago 
Sorry about that - first part is rdamazio

Original comment by rdama...@google.com on 17 May 2011 at 1:44

GoogleCodeExporter commented 9 years ago 
Thanks! Now able to reproduce.

Original comment by rdama...@google.com on 17 May 2011 at 2:14

GoogleCodeExporter commented 9 years ago 
Heh, I feel silly - it's a 2-byte change in the code to fix :)

Original comment by rdama...@google.com on 17 May 2011 at 2:40

GoogleCodeExporter commented 9 years ago 
Please review:
http://code.google.com/r/rdamazio-mytracks-staging1/source/detail?r=46c0a09c60d6
ad3f062ba96d1cd23df4374a2ec3

Original comment by rdama...@google.com on 17 May 2011 at 2:45

GoogleCodeExporter commented 9 years ago 
Done.

Original comment by ba...@google.com on 17 May 2011 at 2:51

GoogleCodeExporter commented 9 years ago

Original comment by rdama...@google.com on 17 May 2011 at 3:01

GoogleCodeExporter commented 9 years ago 
Confirmed resolved in new version 1.1.5RC2. Thanks! I can finally upgrade from 
1.0.21 now!

Original comment by galt...@gmail.com on 17 May 2011 at 3:29

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Hi,

I don't want to register a new issue unnecessarily, but while using the newest 
RC2 version on the drive home I noticed the drawing bug that you referenced (it 
would connect some point in the track to the starting point), and also while 
recording the drive track accuracy looked very low. However, after I stopped 
recording the finished track it must have re-drawn the track and the track 
looked perfectly accurate. Even the long lines that had connected back to start 
point were gone.

Is this all already logged, or do you need more info about this issue?

Original comment by galt...@gmail.com on 18 May 2011 at 11:51

GoogleCodeExporter commented 9 years ago 
Yup, I fixed that bug yesterday, and tested when going home and coming to work 
today - it seems to indeed be fixed. Will send the fix for review shortly.

Original comment by rdama...@google.com on 19 May 2011 at 2:40