Prior to the release of the Garmin Oregon 6x0 series, all devices would record track log data at the user specified rate while always updating Trip Computer statistics once per second. This frequently resulted in users complaining that their Track Log and Trip Computer statistics did not match each other after a hike or other activity.
This page explains why that happens.
The common work-around was to set the tracklog recording settings to manually record a track point once every second to effectively match the Trip Computer recording interval and provide statistics that closely mirrored each other. For many users, this was the only workable solution.
With the Oregon 6x0 (and most new models since), Garmin included additional controls that allow the user to choose when the Trip Computer accumulates data: 'Always' or 'During Activity'. Selecting 'During Activity' alleviates the 'mismatched statistics' issue so often previously reported, while selecting 'Always' retains the legacy behavior for those users who prefer it.
This meant that users could now tie the Trip Computer data accumulation directly to the Tracklog Recording status, freeing them up to use any tracklog recording interval or method they desired instead of being stuck with one track point per second as with the older devices.
Most of those older devices were only capable of using GPS and perhaps WAAS/EGNOS to determine their position, which, when coupled with a once-every-second tracklog recording setting, could lead to some very messy 'spider-web' tracklog recordings each time they encountered a weak signal due to environmental factors beyond their control. These always had to be cleaned up after the fact on a PC or Mac using tracklog editing software.
Newer devices with the additional tracklog recording controls also have access to more GNSS systems and can therefore mitigate some of the 'spider-web' recording issues that were previously unavoidable.
This leaves many users now wondering just what tracklog recording settings they should be using to achieve the best results for their respective activities. And the simple answer is, there is no one setting that will always provide the best results for every user under all circumstances. (but we may get close!)
Using shorter time intervals (such as one track point per second) can result in a recording with the maximum amount of detail, but may require some post processing to thin some of the excessive and unnecessary data after the fact.
Using longer time intervals can reduce the amount of post processing necessary, but only at the expense of losing some detail.
My rule of thumb has always been that activities with slower movement and/or frequent changes in direction require time intervals with more frequently recorded track points. Faster activities, or those with few changes in direction do not require as many recorded track points to retain reasonable accuracy.
Now, you may be slowly hiking some switchbacks one day, and then sprinting down some forest service roads in your ATV the next, and neither activity would benefit from using an identical tracklog recording configuration.
This is where the 'Automatic' settings come into play.
When configured for 'Automatic', the device is always comparing your current position with the last recorded position to calculate when to record the next track point in the tracklog. This setting results in less recorded track points when travelling at higher speeds with little directional change (driving down the interstate) while also allowing detailed path recordings while navigating twisty trails at lower speeds. This means the user can use one setting for multiple activities while achieving acceptable results.
The user can also choose between 'Least Often', 'Less Often', 'Normal', 'More Often', or 'Most Often' to 'fine-tune' the 'Automatic' setting to their liking.
For most of my activities, I find that 'Automatic' and 'More Often' seem to get the job done with satisfactory results, but that may not be true for everyone.
I have yet to be able to find a good use for the 'Distance' based recording intervals.