Altitude jumping from actual position to 0 and insane number of burned calories is displayed

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Import the attached file to see the issue.

What is the expected output? What do you see instead?
The altitude chart contains many 0 altitude points and an insane number of 
burned calories.

What version of MyTracks are you using? On what version of Android? On what
phone?
MyTracks version: v2.06; Android 4.4.3 (CyanogenMod); Samsung S4mini (GT-I9195)

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

Please provide any additional information here:
One day i found some duplicated kmz files on my google drive "my tracks" 
folder, so i simply removed them. After that I found out that on some of them 
there is an altitude and burned calories issue (before it everything was ok).

Original issue reported on code.google.com by grzegorz...@gmail.com on 16 Jun 2014 at 8:21

• Merged into: #1537

Attachments:

• MyTracks_altitude_issue.kmz
• MyTracks_Chart.png
• MyTracks_Statistics.png

[GoogleCodeExporter]

This bug is reported on version 2.0.6.

Please try recording some tracks on version 2.0.7. If it is still happening, 
please file another bug. Thanks

Original comment by jshih@google.com on 10 Jul 2014 at 1:09

• Changed state: Fixed

[GoogleCodeExporter]

It is not fixed.

It still display insane number of burned calories, charts looks a little bit 
better but still altitude jumps to 0.

Original comment by grzegorz...@gmail.com on 10 Jul 2014 at 12:23

Attachments:

• MyTracks_Chart_2.07.png

[GoogleCodeExporter]

Hi grzegorz.jankowski:

The attached kmz file, "MyTracks_altitude_issue.kmz", contains locations 
without altitude value.

Can you confirm that "MyTracks_altitude_issue.kmz" is recorded using My Tracks 
version 2.0.7.

Thanks
Jimmy

Original comment by jshih@google.com on 10 Jul 2014 at 5:37

[GoogleCodeExporter]

Hi grzegorz.jankowski:

Thanks for providing all the info. We found the bug and will have it fixed in 
the next release.

Original comment by jshih@google.com on 10 Jul 2014 at 5:55

• Changed state: Duplicate

[GoogleCodeExporter]

Isn't this a misunderstanding? Is the original problem the chaotic blue line? 
The blue line is speed, not elevation.

Original comment by vojtech....@gmail.com on 17 Oct 2014 at 8:19

[GoogleCodeExporter]

Yeap, you are right :] - but still it is not fixed :P (as well as insane of 
burned calories)

Original comment by grzegorz...@gmail.com on 18 Oct 2014 at 8:26

[GoogleCodeExporter]

Great, it is actually quite funny thing to happen :)

But it is then I think not a bug, but an enhancement to do some kind of speed 
averaging/smoothing, which may be difficult to do well. Well, if it is a 
bicycle or running, than some acceleration values are just not possible, but 
still, it is hard to say, what values really mean a stop and which something 
what should be averaged with something else.

Calories may be a third different bug :)

Original comment by vojtech....@gmail.com on 18 Oct 2014 at 10:12