Basecamp track filtering

Former Member over 13 years ago

I'm new to Basecamp but I think I can already see the benefits of track filtering in analyzing tracks taken from my GPSmap60CSx while hiking. Without filtering the ascent/decent calculations seem way high. In fooling around a little I found that filtering with a minimum distance of 100 or 125 feet seems to get rid of the spikes on the elevation graph. Soes this agree with the experiences of others? Any recommendations on a min distance value to use for filtering?

I see that the Track Filter dialog has an option to filter by minimum time, however the track Properties tab doesn't have a time column. Is this because my device (GPSmap60CSx) doesn't provide time info in the tracks it records? Do some of the newer devices provide time?

Sincere Thanks,
Bill

0 Former Member over 13 years ago

It will have time if you use the raw active track or the archived tracks. If you "save" the track, the timestamps are stripped.... So....never use saved tracks. Turn on the auto archive feature and use those tracks.

0 Former Member over 12 years ago

383943

It will have time if you use the raw active track or the archived tracks. If you "save" the track, the timestamps are stripped.... So....never use saved tracks. Turn on the auto archive feature and use those tracks.

That's true of older devices, and that's probably what's happened in the OP's case, but newer devices have an archive facility that does preserve the timestamps (and I *think* that if you save a track or portion of a track the time data is preserved).

0 Former Member over 12 years ago

If it weren't for the buggy behavior, I think you'd be correct.

That's true of older devices, and that's probably what's happened in the OP's case, but newer devices have an archive facility that does preserve the timestamps (and I *think* that if you save a track or portion of a track the time data is preserved).

In theory, I think you're correct. But I've been encountering "timestamp stripping" (in Basecamp) of tracks originally generated by my Montana 650. Thus far I've been unable to determine exactly when the data is stripped. I suspect it has something to do with transfer to and from the unit with track editing (only editing colors and names of the tracks) done from within Basecamp in between the transfer process. Sometimes it removes the time details (including altitude data) on the properties screen, but keeps the start times (displayed when you filter from the "Swap Data & Map View") intact. ~ So the only way to confirm all the data is still included in the details of each recorded track point is to double click on each track (to open/edit it) and view the properties of the actual track points.

What does seem strange is that once the tracks are "stripped" of this extra data..... It is very apparent that some routine has completely rewritten the XML data of the tracks in a very neat and concise layout. (Without the extra XML fields in the file.) I'm pretty sure the data is not being stripped by the GPS unit. It's happening during the editing/renaming process within Basecamp, as that's where I notice it's missing after editing..... (It may also have something to do with maintaining multiple instances of the same waypoint in multiple lists.) ~ Or, it may be a case of name editing when the new name chose is "invalid" due to the name already in use where the link to the extra data is "broken." (Choosing a new name, or hitting escape "reverts" you to the previous valid name, but this error notification process may somehow be "breaking" the link between the track and the extra time/altitude data.)

PS: I read somewhere that within Basecamp, time and altitude data is NOT actually stored with tracks (in the same file/location.) ~ This data is stored in another file and retrieved/merged when appropriate (which supports the neatly rewritten XML data structure that is missing these these fields/data).....