Basecamp showing two different distances for same track?

Former Member
Former Member
Okay,

249 points in my track. For BASECAMP, the point-by-point view is showing a total distance of 14.7 miles. However, the elevation view is showing 12.2 miles.

Likewise, when I have one point selected in the point-by-point view, I noticed different elevation numbers between the two views. For example, point-by-point for point 100 showing 5024 ft whereas the point selected on the elevation view shows 5038.3 ft.

Comparing the two BASECAMP estimates of distance to what shows on my Oregon 600 - 14.72 mi. the point-by-point view matches. However, the 600 is showing me an elevation gain of 5411. This differs greatly from what is being show in the bottom summary window of the point-by-point view -- 4783 for ascent.

Summary:
MILEAGE
Basecamp point-by-point view (total shown at the bottom): 14.7 mi
Basecamp elevation view (total shown when all points in the point-by-point view are selected): 12.2 mi
Garmin 600: 14.72

ELEVATION GAIN
Basecamp point-by-point view (total shown at the bottom): 4783 ft (ascent); 4579 (descent)
Garmin 600: 5411 ascent / 5202 descent

Interestingly, the ascent/descent numbers show about the same difference between the two calculations (204 ft and 209 ft) - I assume that this could tell me something about the basic error in the GPS. However, I don't know what to make of the differences in the two totals in either the elevation or the miles.

I understand that there are sampling differences. However, it is not obvious to me what they should add up to such a great difference. As sampling inaccuracies should be equally likely to be overestimate for any given point or underestimates they should more, or less, balance out. Hence the differences in the ascent/descent numbers make sense to me.

But what about the large differences between total ascent and total miles?? How far did I walk yesterday??? And how many feet did I climb??

Thanks
  • He does say he has reset the trip data ...

    Sometimes I get that issue if I'm too quick to clear everything after it appears the GPS has a lock. Now I tend to wait 30 seconds or so, that seems to work.
  • Former Member
    0 Former Member over 10 years ago
    I'm getting this same error on an Oregon 600.

    It doesn't matter that I've reset the Trip and Track Log first, some spurious distance data is obtained from somewhere.

    I've noticed that it seems to happen if the unit loses power (intentionally or otherwise) and whether or not I've paused Track Recording before powering off.

    For example, I ride 25km
    I get to the cafe
    I power off the Oregon
    I power it back on and.... it now says I've done 30km

    This is nothing to do with poor satellite reception - that would show as additional Trackpoints.


    There are no additional Trackpoints added to the GPX file but the total distance is too high.

    This error seems to be quite recent. I'm considering reverting to a previous Firmware version
  • Former Member
    0 Former Member over 10 years ago
    Hello Druidh,

    Please post back here if you find a way to go back to a previous firmware and how well it works.

    I have an Oregon 600 and am interested in what happens.

    Thanks,
  • Former Member
    0 Former Member over 10 years ago
    He does say he has reset the trip data ...

    Sometimes I get that issue if I'm too quick to clear everything after it appears the GPS has a lock. Now I tend to wait 30 seconds or so, that seems to work.


    I think this hits the nail on the head! Wait for GPS to lock, wait a bit longer, then clear both trip and track seems to be the answer. I have not seen this problem since updating to firmware 4.20, but that might be due to this more careful start up procedure. I was not aware that trip computer data gets transferred to the track log. That explains a few things. But nothing explains why the trip odometer jumped by 5 miles near the start of my walk. That seems like buggy software. Maybe 4.20 fixed that?
  • I think this hits the nail on the head! Wait for GPS to lock, wait a bit longer, then clear both trip and track seems to be the answer. I have not seen this problem since updating to firmware 4.20, but that might be due to this more careful start up procedure. I was not aware that trip computer data gets transferred to the track log. That explains a few things. But nothing explains why the trip odometer jumped by 5 miles near the start of my walk. That seems like buggy software. Maybe 4.20 fixed that?


    If you reset before the lock the millage will be wrong. This is easy to see in BaseCamp you will have a straight line from where you powered down to where you powered up.

    Garmin did have a bug that could add or subtract mileage to the trip computer and I have seen errors of more then 5 the miles you had with this bug. You can see this by forcing BaseCamp to recalculate the distance instead of using the summery information and it will come out correct. This bug was fixed in version 4.20 (eTrex the version with the fix will have have different numbers for other units). I have been happy with the fix on my eTrex 20 and my GPSMAP 64s. They both had problems but after the fix have been good.