search

irfan-arshad-arbisoft / mytracks

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

Issue 1454 elevation gain error, not fixed in version2.0.7 #1537

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
I'm only opening up a new report for this, since tbe previous issue is mareked 
as fixed. I've seen people (myself included) posting at the end of Issue 1454 
that the problem is not fixed. I'm not sure if anyone is still monitoring Issue 
1454 because of its  status being fixed. So here is a new issue to hopefully 
open a new bug report for this. 

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?

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

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 dbonb...@gmail.com on 21 Jun 2014 at 10:47

GoogleCodeExporter commented 9 years ago 
The elevation gain bug has not been fixed with version 2.0.7 update.
I had to go back to 2.0.5 version.  I am using Samsung Galaxy Note 2.

Original comment by hansong...@yahoo.com on 23 Jun 2014 at 3:07

GoogleCodeExporter commented 9 years ago 
I can confirm that this issue is NOT fixed.  I just used the app last night 
(July 2) and my starting elevation was recorded as gain.  PLEASE fix this! 
Elevation gain is a key parameter!

Original comment by dean.dan...@gmail.com on 3 Jul 2014 at 6:52

GoogleCodeExporter commented 9 years ago 
Hi Guys:

Can you post a track that contains the wrong elevation gain in kml/kmz format?

Thanks
Jimmy

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

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Here you go.

Original comment by patrick....@gmail.com on 10 Jul 2014 at 1:04

Attachments:

GoogleCodeExporter commented 9 years ago 
Hi Patrick:

I imported the kmz file to my phone and have the elevation gain of 661.55 ft.
Can you tell me what the elevation gain is on your phone? Can you include a 
screenshot?

Thanks
Jimmy

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

GoogleCodeExporter commented 9 years ago 
661 is what my phone says. But that is wrong. Should be about 300 feet.

Original comment by patrick....@gmail.com on 10 Jul 2014 at 1:21

GoogleCodeExporter commented 9 years ago 
Here's a kmz, and a screenshot. In a 30 second recording on my couch, it shows 
my gain of over 5000'. It's also my starting elevation.

Original comment by dbonb...@gmail.com on 10 Jul 2014 at 2:52

Attachments:

GoogleCodeExporter commented 9 years ago 
Hi patrick.k.sloan:

The elevation gain is the sum of all the elevation gains during a recording. 
Why do you feel it should be 300 feet instead of 661 feet?

Jimmy

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

GoogleCodeExporter commented 9 years ago 
Found the bug. Targeting the next release.

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

GoogleCodeExporter commented 9 years ago 
Hi Jimmy, that is a poor example.  I was having trouble uploading from my 
phone. 

Here is a more clear example.  traveled 1835 feet, but gained 2259 feet of 
elevation?

Original comment by patrick....@gmail.com on 10 Jul 2014 at 5:47

Attachments:

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

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

GoogleCodeExporter commented 9 years ago 
Its been "fixed in next release" for a year or more. I'm not holding my 
breath...

Original comment by rwz...@gmail.com on 12 Jul 2014 at 2:29

GoogleCodeExporter commented 9 years ago 
When will be done next release?

Original comment by MyT...@gmail.com on 12 Jul 2014 at 8:03

GoogleCodeExporter commented 9 years ago 
eta?

Original comment by patrick....@gmail.com on 21 Jul 2014 at 7:38

GoogleCodeExporter commented 9 years ago 
Any update on the next release?

Original comment by patrick....@gmail.com on 7 Aug 2014 at 8:47

GoogleCodeExporter commented 9 years ago 
As of August 13, still getting massively generous elevation gains.  Any idea 
when the fix is in?

Original comment by riptider...@gmail.com on 13 Aug 2014 at 7:43

GoogleCodeExporter commented 9 years ago 
I have noticed that if you pause recording, the altitude that you are at, at 
the moment that you restard recording, is also added to elevation gain.

Original comment by matija.a...@gmail.com on 17 Aug 2014 at 7:41

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

Original comment by jshih@google.com on 13 Oct 2014 at 6:25

GoogleCodeExporter commented 9 years ago

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

GoogleCodeExporter commented 9 years ago 
We addressed another elevation gain bug in version 2.0.8.

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

GoogleCodeExporter commented 9 years ago 
Where can we find version 2.0.8?

Original comment by patrick....@gmail.com on 13 Oct 2014 at 9:59

GoogleCodeExporter commented 9 years ago 
And how do you find this version 2.0.8?

Original comment by patrick....@gmail.com on 13 Oct 2014 at 9:59

GoogleCodeExporter commented 9 years ago 
I was able to download 2.0.8 and install it today from the play store.

Issue is *not* fixed.   It now reports elevation gain of 0 feet even when the 
rout takes you up and down in elevation.

Original comment by patrick....@gmail.com on 16 Oct 2014 at 11:06

Attachments:

GoogleCodeExporter commented 9 years ago 
Issue https://code.google.com/p/mytracks/issues/detail?id=1530 - not fixed as 
well.

Original comment by grzegorz...@gmail.com on 17 Oct 2014 at 7:11

GoogleCodeExporter commented 9 years ago 
Wow, This bug has existed since January and there's been only 2 updates since 
then with no resolution. I've kept version 2.0.5 because of this, and will not 
upgrade until this is confirmed fixed. I wish I could use another app, but none 
of the others I've tried have the functionality I like from MyTracks. I'd 
suggest someone open up a new bug report, since this one is marked fixed I 
don't think posting on this bug will help the cause anymore.

Original comment by greatwes...@gmail.com on 17 Oct 2014 at 2:02

GoogleCodeExporter commented 9 years ago 
Hmm, in 2.0.8 it works for me. Remember, that gain is not "max elevation" - 
"min elevation". If you go downhill, you do not gain elevation.

Original comment by vojtech....@gmail.com on 17 Oct 2014 at 7:49

GoogleCodeExporter commented 9 years ago 
Elevation readings can be noisy, especially in the beginning when gps tries to 
obtain a fix. Thus we wait until we have buffered at least 25 readings before 
displaying the values. Thus it might appear to be zero in the beginning since 
we do not have high confidence of their accuracy in the beginning.

Original comment by jshih@google.com on 17 Oct 2014 at 11:29

GoogleCodeExporter commented 9 years ago 
Tried a longer track and indeed the gain did start populating.  Looked to be 
reasonably accurate as well.  Thanks for the fix.

--pat

Original comment by patrick....@gmail.com on 20 Oct 2014 at 2:30