Several things can happen when a GPS is having difficulty getting good signals (either due to an inferior (compared to the latest and greatest) GPS or a poor skyview):
* It may record some inaccurate points. (Often the first and last couple points in a continuous section of track are less accurate than the others.)
* There may be gaps in the track (ie no points for sections of the route).
Background: The track log in my Garmin GPSes (presumably other brands are similar) consists of:
* One or more named tracks (<trk> in GPX)
* Each named track consists of one or more track segments (<trkseg> in GPX)
* Each track segment consists of some number of track points (<trkpt> in GPX)
Turning the GPS on and off will generally begin and terminate a named track in the track log. A long period with no signal will break a named track into multiple segments, but might also break it into multiple named tracks.
When I get a good signal for the entire trip (ie use my 60CSx...
), I often get the entire trip in a single track segment in a single named track.
If I have sections where there was no signal (ie went through a long tunnel), then a named track is likely to be broken into multiple track segments (or possibly multiple named tracks).
The easiest way to examine the structure of a track might be to either download it as a GPX file or convert it to a GPX file (MapSource or GPSBabel can do either:
www.gpsbabel.org) and examine the resulting text file. The format is very human readable and I've mentioned some of the tags above. (You can also edit it in this format as well.)
The next question is how a computer program (or your GPS) displays a track. In the ideal case (all points are accurate and in a single track segment), all sequential points are connected by straight lines in the display. (I think this is how most displays work.) The issues come up about what to do with separate track segments: Do you simply connect them as if they were parts of a single track or do you put gaps in the display? Presumably the software author makes some choice or in one of my programs allows the user to select a policy. If you draw straight lines between the ends of track segments or named tracks, the lines can be wildly inaccurate with respect to the path that you actually took.
It looks to me like your image is from Garmin MapSource. IIRC, MapSource does not connect between track segments. It looks to me as if your track has a number of inaccurate points, has gaps, and is broken up into many segments (or many named tracks). (It would have been much cleaner, prettier, and more useful if you had used your 76CSx. You likely could have avoided the bivy...)
In Mapsource:
If you click on the "tracks" tab, you will see a listing of the track segments and if you double click on a track segment (in the tab) you will see a listing of the individual track points. You can also see the same thing by examining the corresponding GPX file.
In the GPS Bakeoff we recorded simultaneous tracks of 7 GPS/antenna combinations. The tracks are available for download (from the thread) if you want to view them. The difference bewteen the eTrex Vista and the 60CSx (electrically identical to the 76CSx) is dramatic...
http://www.vftt.org/forums/showthread.php?t=14406. In fact, I bought my 60CSx as a result of this experiment.
Doug