Why can't the 66i record a reasonably accurate elevation track when in expedition mode?

Why can't the 66i record a reasonably accurate elevation track when in expedition mode?  Expedition mode is tremendously valuable for certain applications like long backpacking hikes.  But documentation that I can find is scant.

Please don't dismiss my question.  I already know the design purpose for relaxing tracking accuracy is to reduce power consumption.  And I already know Garmin doesn't publish its firmware source code.  I'm looking for an answer of detail somewhere in between.  In other words, "How does expedition mode save power?"

The lateral tracks are somewhat less accurate in expedition mode but still useful.  The elevation record associated with those tracks however, is so wildly off target that it probably should not even be recorded.

Is it doing less processing?  Is it turning the receiver off in between track points?  If that were true, then users could alter power by changing tracking point frequency.  Are there elevation settings that would change the accuracy of elevation tracks in expedition mode?

Next, is there anything I can do to get a more accurate track without grossly increasing power consumption?  Then, is there anything Garmin could do to its firmware code?

  • If I were going down a short hill, elevation change of 49 - 60 ft, in a minute or so, I would use barometric elevations.  If I were going up and down backpacking in the mountains for a week with significant weather changes predicted, I would use GPS derived elevations.

  • Good point, CowboySlim.  But I'm not sure it addresses my question.  Would elevation tracks be reasonably accurate in expedition mode if elevation were derived from gps data?  I don't think so, but I'm not sure.

  • Actually, I have recorded dozens of both barometric and GPS derived elevations and performed correct statistical analyses.  I am not speaking from propositional guesswork.

  • Thanks, CowboySlim.  I didn't mean to imply you were spouting speculation.  Based on my experience, I think everything you wrote is correct.  The problem is that it may be off point.  My question has to do with elevation tracks in expedition mode.  From my experience the elevation accuracy between expedition mode and regular mode is vast.

  • I will post shortly how you can make your own calculations and then make your own judgements.

  • Thanks, CowboySlim. Also, if you know a way to set elevation tracking to use gps elevation, I'm not aware of how to do that.  Does setting altimeter calibration to "continuous" accomplish that?  Also, I wonder how much power is consumed by the "continuous" setting when in expedition mode.

  • Sorry about my shortly comment, got caught up in NFL.  However, I will describe my mehtodology,as calculating the precisions of various methods by determining the standard deviations for compariosons quantitatively.  This is what I use"

    https://en.wikipedia.org/wiki/Normal_distribution

    Back tomorrow. 

  • From jig2: (1) “ Would elevation tracks be reasonably accurate in expedition mode if elevation were derived from gps data?  I don't think so, but I'm not sure.” (2) “Also, if you know a way to set elevation tracking to use gps elevation, I'm not aware of how to do that.  Does setting altimeter calibration to "continuous" accomplish that?  Also, I wonder how much power is consumed by the "continuous" setting when in expedition mode.”

    Answers: (1) Perform the determinations of the relative precisions (standard deviations of normally distributed data) as described below and you can make that resolution yourself. (2). I am not sure if that can be done. I posed that question a year, or so, ago on the geocaching technical forum. I received a mess of nonsensical gibberish, none of which was informative. I requested, but never received a keypunch by keypunch sequence by which I could impose a continuous stream of GPS derived elevations. My presumption is that selection of Continuous will provide that while not recording; however, starting recording will switch back to barometric.

    Calculations in a while.

  • Thanks, CowboySlim.  

    To measure the accuracy in standard deviations, I think I would need many devices or leave one device in the same place for awhile.  The second approach would not help because of the nature of the inaccuracy.  

    I should have been more specific in my original post.  The elevation record errors I'm referring to are enormous compared to your assumption here.  The track will show usually wrong elevation well correlated from one recorded point to the next.  Then it will change by perhaps 1000 feet or more between adjacent record points a minute or two apart and then resume good point-to-point correlation going forward until the next crazy change in elevation.  Even when adjacent points are well correlated, they can be more than 1000 feet off.

    To repeat what I said originally, this is only in expedition mode.  My 66i gives reasonably good elevation tracking when not in expedition mode.  I haven't done rigorous testing to know.  So it's possible the crazy changes in elevation match times when I take the device out of expedition mode to check my track on its internal map or to send or receive an InReach message.

  • Yes, that could be.  I have no experience with expedition mode.