NickM said:
That's very handy to know - thanks
Stevew, don't give up on your eTrex! As long as it can accomodate 100+
trackpoints at a time (mine seems to hold 124) it's very useful for cycling when used in "compass arrow" mode in conjunction with a track loaded from OS mapping software. Planning a ride on the PC in advance has the great advantage of keeping you away from unpleasantly busy roads and awkward junctions, while still allowing exploration. My yellow eTrex and Tracklogs mapping have been a tremendous aid to cycling pleasure. All the more so since my eyesight is no longer up to reading map detail or a route sheet on a bumpy road.
Yes, NiMH cells that didn't auto-discharge so quickly would be good! I gave up expecting my NiMH batteries to hold a charge for long periods and got into the habit of always charging mine overnight before a ride.
I never quite understood the difference between
trackpoints and
waypoints, and therefore
tracks and
routes. I always thought one plotted waypoints to build up a route and that a track was what the GPS stored to show the actual course taken?
I've noticed that the Etrex tracklog of a ride is basically an approximation. The device seems to calculate where it will be at the end of the next sample period based on current speed and bearing and takes the next reading when it thinks it should have got there. My evidence for this is that the part of a tracklog relating to a fast switchbacked descent repeatedly 'overshot' the bends by 50 metres or so, much more than the actual GPS error. The same descent ridden more slowly was tracked correctly.
I didn't like navigating in
compass arrow mode having tried it out on foot when I first got my Etrex. I plotted a walk past the local Post Office, then along a canal towpath. I tried to imagine being on the bike in traffic. It was okay when I was some distance away from a turn at some traffic lights but then as I got closer, the arrow started pointing in the wrong direction! If I was on my bike I'd have got in the right hand lane and signalled right whereas I actually wanted to go left. I deduced that the GPS error and perhaps an error in plotting the waypoint had added together to put the 'virtual waypoint' to the right of the actual junction. I followed the arrow which then promptly flipped round to point to the next waypoint which was by then behind me! I persevered and walked down the road past the P.O. and the whole time the arrow was pointing to my left as if telling me that I should be the other side of the building. On foot I could work out that this was due to the inherent error in the GPS reading but I wouldn't like to worry about that in traffic.
After that I switched to using
breadcrumb trail mode and found that to very satisfactory. I can tell at a glance when I am approaching a waypoint and where I will be going after that so I can get in the correct lane, adjust my speed, whatever. It is helpful to label the waypoints using the system suggested
here so one can see in advance which exit to use at a roundabout for example. It is also necessary when navigating a complex junction where GPS error can lead to doubt as to exactly which road to take. I've only got confused at what the Etrex is telling me when I haven't bothered to label the waypoints. If I was tackling a roundabout, leaving by the 2nd exit, and then turning immediate right, I'd label it
xxxE2R where
xxx is the waypoint number. The numbering is necessary because the Etrex needs to have a unique label for each waypoint and it isn't wise to let it rename them itself (which it will do if you don't!). What I'm saying is that you can't have 2 or more labels such as
L so call the first one something like
023 L and a subsequent one
097 L (whatever). It obviously makes sense to number them in the order they occur on the route. If I am following an audax route I usually copy the labels onto the relevant parts of the routesheet in case I have to refer to it (which I rarely have to now).
One other thing - the Etrex navigation trail can be displayed at different resolutions which can be changed 'on the fly' or set to auto-range. It can be a bit confusing if one isn't sure of the resolution being used because a quick glance at the GPS screen might make one think the next waypoint is closer or further away than it actually is. Riders who have ridden with me when I'm using the GPS know that I call out of most the turns in plenty of time, but a few times I've had the screen resolution wrong and we've missed the turn.
The great thing about navigating by GPS in this way is that it mistakes are obvious in seconds. I'd probably only make four or five 'two second' mistakes in a typical 200 km audax whereas my more experienced audax mates frequently end up on 5 or 10 km detours when they make mistakes interpreting their routesheets. I know which I prefer

!