search

djodjoni / mytracks

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

version 2.05 chart elevation starts at zero #1355

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. My Tracks...Settings...Chart, ensure Elevation is checked
2. Select recorded track, select Chart display

What is the expected output? Same as the previous My Tracks version—Elevation 
chart baseline is just below lowest point in Track and maximum is a reasonable 
amount higher than the highest point in the track (see chart_elevation_My 
Tracks v1.x.png attachment).

What do you see instead? Elevation chart baseline is zero (0) feet, maximum is 
12,500 feet.  (see chart_elevation_My Tracks v2.05.png attachment)

What version of MyTracks are you using? 2.05
On what version of Android? 4.1.2
On what phone? SPH-L900 (Samsung Galaxy Note II)

Original issue reported on code.google.com by ed.r.b...@gmail.com on 12 Aug 2013 at 9:27

Attachments:

GoogleCodeExporter commented 9 years ago 
If you can export your track in both csv and kml, it will help us reproduce the 
cause?

Export -> External storage -> as CSV and as KML, email yourself a copy and 
include in the bug report.

Original comment by jshih@google.com on 12 Aug 2013 at 9:36

GoogleCodeExporter commented 9 years ago 
Hi jshih,

Thank you for your rapid reply.  I have attached a .csv snippet of the 
beginning and end of the v2.05 chart which perhaps show the likely problem:  
there is no Altitude data in the first two rows which, since it is missing, is 
probably interpreted as zero (0) by the charting program, leading to the 
vertical-axis scaling error.  There is no such problem in the v1.x file; it has 
altitude data in the first row.

Please note that, for reasons of privacy protection in this public forum, I 
have deleted the lat/long data, and have not attached the kml data you 
requested.  I hope that this does not affect your ability to interpret the data 
and determine the cause of the missing altitude information.  If you need the 
complete data sets, please let me know, and I'll send them directly to your 
google.com email address.  Finally, if there is any further testing that I can 
do to help you sort the problem, feel free to ask.

Original comment by ed.r.b...@gmail.com on 12 Aug 2013 at 11:39

Attachments:

GoogleCodeExporter commented 9 years ago 
Troubleshooting Update:

1. Disabled all three Location Services (Use wireless networks, Use GPS 
satellites, Location and Google search)
2. Re-enabled two Location Services (Use GPS satellites, Location and Google 
search)

After taking these two steps, the failure to initialize the Altitude in the 
first one or two rows of data HAS GONE AWAY.  In other words, My Tracks v2.05 
now works as expected.

Unfortunately, I didn't take a data sample immediately before dis- and 
re-enabling the Location Services steps, so I cannot tell if the problem "fixed 
itself" some other way (i.e. via some unseen product update), so I do not know 
if this problem should be marked as resolved.  Your thoughts,jshih?

Original comment by ed.r.b...@gmail.com on 14 Aug 2013 at 8:11

GoogleCodeExporter commented 9 years ago 
This can be a temporary workaround. But the real fix is that My Tracks should 
ignore on the chart view any data (from wifi) that doesn't contain elevation 
values.

Thanks for the update
Jimmy

Original comment by jshih@google.com on 14 Aug 2013 at 8:34

GoogleCodeExporter commented 9 years ago 
Hello,
I have same problem like reporter of this bug. But his Hot-Fix isn't working 
for me. Is there any progress on this problem?

What version of MyTracks are you using? 2.0.5
On what version of Android? 2.3.5
On what phone? HUAWEI U8650

Original comment by martin.s...@gmail.com on 24 Jan 2014 at 3:22

GoogleCodeExporter commented 9 years ago 
I believe this issue is directly related the way the OS handles locations 
settings, see this issue: 

https://code.google.com/p/mytracks/issues/detail?id=1446&thanks=1446&ts=13910325
54

Original comment by homebran...@gmail.com on 29 Jan 2014 at 11:06

GoogleCodeExporter commented 9 years ago 
Yeah, it seems possible. But everything was alright with previous version of 
MyTracks. If this problem is not solved, I will move the other tracking 
software...:(

Original comment by martin.s...@gmail.com on 30 Jan 2014 at 8:18

GoogleCodeExporter commented 9 years ago

Original comment by jshih@google.com on 31 Mar 2014 at 5:23

GoogleCodeExporter commented 9 years ago 
Hello jshih,
can you please specify when new version with fixed bug will be released? Thank 
you...

Original comment by martin.s...@gmail.com on 31 Mar 2014 at 7:30