Recording a track, mileage drops upon finish

Answered

Follow

jdrewelow

• March 23, 2019 01:47

This is a minor, but annoying issue.  Whenever I "finish" a track, the mileage data decreases by a few tenths of a mile.  For example, I went on a short hike today and when I "paused" at the finish my reading was 4.72 miles.  But then I "finished" the track and the mileage dropped to 4.48 miles.  This happens on every hike I do, the mileage always drops by a few tenths when I hit the finish track button.  Does anyone know why this occurs?

0

• 

  kb1zhs

  • March 23, 2019 07:34

  I had the same issue three days ago. At the end of a hike mileage showed 7.04 but after finishing it was 6.4.

  what’s up with that?

  0

  Comment actions Permalink
• 

  nanlloy

  • March 24, 2019 19:50

  At the end of a hike yesterday, the el. gain showed over 4,800'.  The mileage was close to our 11 mile estimate.  The hike leader disagreed with Gaia and believed the total gain s/b around 3,900'.  Another member of my group showed over 4,500' gain, and someone else had closer to 3,500'.

  When I got home after driving more than an hour, I was shocked to see the el. gain had changed to 3,668'!  How is that possible?  Two things: I had stopped recording the track at the trailhead - can the stats still change?  Also, Gaia continually updated during the trip but three of us had three different results at the end, all of them hundreds of feet off.

  After getting home, I created a route on my laptop following the exact track I had recorded, and came up with 3,968'.  This is more in line with the trip leader's estimate.

  Can you explain how/why this happened?  I've been using Gaia for several years and this is the first time such discrepancies have come up.  Thank you.

  0

  Comment actions Permalink
• 

  Robyn

  • March 27, 2019 16:20

  Hi Everyone, I'm sorry you are seeing discrepancies in your track recording stats after the track is saved. We recently found out about this issue and have a fix available in the most recent version of the app (version 1.8.2).

  @nanlloy Gaia GPS uses your phone built-in GPS chip to calculate elevation. It sounds like each phone was experiencing different levels of GPS drift which the app tries to account for by filtering GPS information. This can result in different reports in elevation stats between devices.

  0

  Comment actions Permalink
• 

  jdrewelow

  • March 28, 2019 00:40

  Thanks for the your response Robyn and I'm glad to hear you have a fix already identified for this issue.  When will version 1.8.2 be released?

   

  0

  Comment actions Permalink
• 

  kb1zhs

  • March 28, 2019 09:57

  Version 1.8.2 is available for download in The App store now. 03/27/19.

  0

  Comment actions Permalink
• 

  jdrewelow

  • March 28, 2019 14:30

  Awesome, thanks!

  0

  Comment actions Permalink
• 

  kb1zhs

  • March 28, 2019 14:47

  I tried the 'beta' version of the Gaia GPS software on Tuesday with 3 different trips and the pre & post ( after finishing & saving ) mileage was the same. I installed the app store version 1.8.2 yesterday and am heading out to try it shortly.

  0

  Comment actions Permalink
• 

  kb1zhs

  • March 28, 2019 20:28

  Just got back from a hike using the 1.8.2 version of Gaia GPS I downloaded from the App Store. Mileage tracking worked fine...no difference in mileage when I 'finished' the tracking.

  0

  Comment actions Permalink
• 

  jdrewelow

  • March 30, 2019 01:24

  I've gone on a couple hikes now with version 1.8.2 and my mileage tracking issues appear to be solved.  No more discrepancies when "finishing" a track.  I'm super happy about this and appreciate the great customer service from GAIA.  Thanks!

  0

  Comment actions Permalink

Please sign in to leave a comment.