RINO 110 timestamp question.

[Neil]

My tracklog files all have the exact same time of day for each trackpoint. How do I get my unit to register the correct time for each point?

[redhawk]

Walk slower!!

[Kevin]

I believe that means you're importing each track as individual waypoints and not as a continuous stream of data (a 'track'). Waypoints don't consider time stamping since it's used for marking a spot arbitrarily, but track(s) logs are time stamped for planning reasons (speed estimates, etc).

[JJW]

Neil wrote: "My tracklog files all have the exact same time of day for each trackpoint. How do I get my unit to register the correct time for each point?"

Neil,
On my GPSr if you download the active track you get the correct time stamps,
If I save a track and then download the saved track, I loose the correct time.

This may be what is happening with your unit?

Good Luck,
John

[Neil]

I wonder if the unit stamps all of the trackpoints with the time of day that you saved the track. Definitely not a good thing if that's the case.

[Rich Owings]

On my GPSr if you download the active track you get the correct time stamps,
If I save a track and then download the saved track, I loose the correct time.

This is normally the problem when this happens. The best solution (barring extended, multi-day trips away from a computer) is to download the active track as soon as you return.

Rich Owings
www.MakeYourOwnMaps.com
www.GPStracklog.com

"We were desert mystics, my friends and I, poring over our maps as others do their holy books." - Edward Abbey

[Neil]

This is normally the problem when this happens.

This is the kind of thing that drives me nuts. Why in the world would you want to lose all that data? The whole point of saving something is to "save" data, not throw it out. It can't be related to file size because each saved trackpoint has a timestamp, the wrong one. When I mentioned this problem to the guy at the Garmin repair counter he gave me a wonderfully eloquent answer: he shrugged his shoulders.

I don't know how many trackpopints you can save in a single tracklog but for multi day, multi trip excursions the workaround seems to be simply to create one big tracklog and then cut it up on the PC when you get home. You get very long straight lines that run from the end of one trip to the beginning of another. Once you delete the last, then first trackpoints of two sequential hikes those line should dissapear.

[redhawk]

It's a GPS, not a Journal or Almanac!!

[JJW]

Neil,
Garmin should have called saved tracklogs "Compressed" tracklogs because of the large amount of data they cut-out.

Your Rino 110 is just the most basic Rino unit.
It is quite limited on internal memory.

Your "active" tracklog can only store 3,000 points. :-(

Your "saved" (compressed) tracklogs are limited to 250 points each. :-(

Looks like you are ready to upgrade. ;-)

Good Luck,
John

[Neil]

Yeah but I think the 120 and the 130 do the same thing with the "saved" tracklog.

[JJW]

Yes, all Garmin "saved" (compressed) tracklogs discard data to save memory space.

I checked Garmins website and the Rino 130 can have up to 10,000 points in the active tracklog and 20 "saved" tracks with 250 points in each.
The new Rino 530 can have up to 10,000 points in the active tracklog and 20 "saved" tracks with 500 points in each.

All Garmins "saved" tracklogs throw out the data with the the correct timestamp.

Good Luck,
John

[Neil]

I went for a 5 mile walk today and carried my 110. I set up the trackpoint interval to "most often" and used 12% within 2½ mi. Then I set it it to "least often" for the next 2½ mi and used only 4 more %. 2½ x 25 = 62.5 miles. The only thing is I don't know if the intervals were time or distance based. I had record method set to "Auto". I walk or jog that route often so will try all the options.

While I was at it I tried out the trackback function. Guess what? You have to save your tracklog before using this function. Of course you can record a new tracklog right over top of the old and download that without saving.