What is "auto" mode for tracking on Garmin eTrex Vista C?

[kr.afol]

I have a Garmin eTrex Vista C. When it is tracking, you can have it in one of three modes: Distance, Time, and Auto.

 

Now, it's pretty clear what is going on in Distance and Time mode, it records your location at fixed distance or time intervals.

 

But what is it doing in Auto mode? The manual rather unhelpfully says that it is by "frequency". But frequency of what? I've taken a look at the tracks produced and I can't see any obvious pattern (my initial theory was change of bearing but that doesn't seem to stack up against the data).

 

So I was wondering if anyone knows?

[+Chuy!]

You are referring to when the GPS records tracks - semantics, but now I get it.

 

I'm not sure how it records tracks in auto mode either, but I set mine to .01 miles. Kinda like recording in superfine instead of normal. This records tracks as accurately as possible; if set to time it records the short steps you take when you take a rest, giving you a false distance reading. Distance is also very important on a bike as a time setting 'cuts' corners (especially sharp ones).

[+WVRadar]

Do you know if setting the tracking mode to "distance" instead of "auto" will cure the Trip Odometer bug on the eTrex Vista? I have an eTrex Venture HC, but it also has this bug.

[+apersson850]

Automatic mode records points based on when needed.

You can imagine the function, in two dimensions, like this:

 

Start out from some point, to get an initial condition. Store that point.

Move some arbitrary distance. Store that point too.

Now draw a line between these two points, passing point two, thus projecting into your (possible) future.

As long as you keep moving along that line, do nothing.

When you stray off the line by some amount of distance (this is where the sensitivity setting of Auto recording comes in), store a new point where you are now.

Draw a new line from your second last point through your last point, and repeat the process of checking how near that line you are, to determine if a new point should be stored.

 

This description is only for two-dimensional positions. Now add a similar algorithm for speed and elevation changes, and you have the whole scenario in front of you.

 

The advantage of automatic mode is that it doesn't waste memory, as it will not spend points every set distance/time, if there is nothing to tell (steady state), but stores several points when you do intricate manouvers.

[+Chuy!]

Do you know if setting the tracking mode to "distance" instead of "auto" will cure the Trip Odometer bug on the eTrex Vista? I have an eTrex Venture HC, but it also has this bug.

 

No, because these settings are only when recording tracks. The odometer bug, as far as I can tell (because mine don't have this bug) is when ths GPs is in non-track-recording mode. That is, your GPS starts 'recording' data as soon as you turn it on as displays the info on the odometer page.

[kr.afol]

Automatic mode records points based on when needed.

You can imagine the function, in two dimensions, like this:

 

Start out from some point, to get an initial condition. Store that point.

Move some arbitrary distance. Store that point too.

Now draw a line between these two points, passing point two, thus projecting into your (possible) future.

As long as you keep moving along that line, do nothing.

When you stray off the line by some amount of distance (this is where the sensitivity setting of Auto recording comes in), store a new point where you are now.

Draw a new line from your second last point through your last point, and repeat the process of checking how near that line you are, to determine if a new point should be stored.

 

This description is only for two-dimensional positions. Now add a similar algorithm for speed and elevation changes, and you have the whole scenario in front of you.

 

The advantage of automatic mode is that it doesn't waste memory, as it will not spend points every set distance/time, if there is nothing to tell (steady state), but stores several points when you do intricate manouvers.

 

OK. so I was on the right track (so to speak) in thinking it was change of direction that would trigger a recording, as it seemed to me that recording changes would be the most efficient in terms of points. However, as the reporting has a 2D bearing which often appeared to be the same for successive (and often short) legs, I was thinking my theory didn't fit the data I was seeing. However, it may have been that there was a sufficient change altitude or speed that was causing the recording of the point. That makes sense.

 

It's perhaps worth explaining why I am so interested in how the tracking is being done. We went on a month's holiday recently driving from Brisbane to Perth and back (about 12000 km) and we were using the Garmin to record waypoints and tracks in the hope we could automatically (or at least semi-automatically) geo-locate our photos. Now in the 2 years we've owned the Garmin, we've never had a problem with recording track data. All the track data we've ever recorded was still fitting in the memory, but with the benefit of hindsight, it was a large number of fairly short trips. So we set off to Perth with the tracking on, assuming we'd have a month of track data on our return. Sadly we found we had about 4 days of track data because the Garmin didn't have sufficient memory and was overwriting. So, I'm now very motivated to try to work out the best settings for trackings to make the most efficient use of the memory to avoid this problem in future (I'd rather not have to cart a laptop around just to upload track info). But of course the solution might lie in getting a camera with a builtin GPS (still a bit of an expensive option but probably the preferred option in terms of what we are actually trying to achieve) or getting another GPS with more track memory.

 

Thanks for everyone's thoughts.

 

Kerry

[SiliconFiend]

Automatic mode records points based on when needed.

You can imagine the function, in two dimensions, like this:

 

Start out from some point, to get an initial condition. Store that point.

Move some arbitrary distance. Store that point too.

Now draw a line between these two points, passing point two, thus projecting into your (possible) future.

As long as you keep moving along that line, do nothing.

When you stray off the line by some amount of distance (this is where the sensitivity setting of Auto recording comes in), store a new point where you are now.

Draw a new line from your second last point through your last point, and repeat the process of checking how near that line you are, to determine if a new point should be stored.

 

This description is only for two-dimensional positions. Now add a similar algorithm for speed and elevation changes, and you have the whole scenario in front of you.

 

The advantage of automatic mode is that it doesn't waste memory, as it will not spend points every set distance/time, if there is nothing to tell (steady state), but stores several points when you do intricate manouvers.

 

OK. so I was on the right track (so to speak) in thinking it was change of direction that would trigger a recording, as it seemed to me that recording changes would be the most efficient in terms of points. However, as the reporting has a 2D bearing which often appeared to be the same for successive (and often short) legs, I was thinking my theory didn't fit the data I was seeing. However, it may have been that there was a sufficient change altitude or speed that was causing the recording of the point. That makes sense.

 

It's perhaps worth explaining why I am so interested in how the tracking is being done. We went on a month's holiday recently driving from Brisbane to Perth and back (about 12000 km) and we were using the Garmin to record waypoints and tracks in the hope we could automatically (or at least semi-automatically) geo-locate our photos. Now in the 2 years we've owned the Garmin, we've never had a problem with recording track data. All the track data we've ever recorded was still fitting in the memory, but with the benefit of hindsight, it was a large number of fairly short trips. So we set off to Perth with the tracking on, assuming we'd have a month of track data on our return. Sadly we found we had about 4 days of track data because the Garmin didn't have sufficient memory and was overwriting. So, I'm now very motivated to try to work out the best settings for trackings to make the most efficient use of the memory to avoid this problem in future (I'd rather not have to cart a laptop around just to upload track info). But of course the solution might lie in getting a camera with a builtin GPS (still a bit of an expensive option but probably the preferred option in terms of what we are actually trying to achieve) or getting another GPS with more track memory.

 

Thanks for everyone's thoughts.

 

Kerry

If your model has a microSD slot, you can (and should) set it up to record the tracklogs to the card. You'll get one GPX file per day, and they aren't overwritten.

[SiliconFiend]

If your model has a microSD slot, you can (and should) set it up to record the tracklogs to the card. You'll get one GPX file per day, and they aren't overwritten.

Oops, I just saw that you mentioned you had a Vista C, not a Cx or HCx. Well, something to think about if you're considering upgrading.

[+apersson850]

There are also units like the Zumo and the Colorado, which archive their logs to internal flash memory when the active log runs out of track points.