[pct-l] Follow-up to the earlier GPS discussion

[CHUCK CHELIN]

Good morning, Melanie,

I’d like to offer a somewhat different view of GPS usage on the PCT.  I
don’t consider a GPS to be mandatory because thousands of people have hiked
the PCT without one.  Indeed many hikers don’t understand or try to do any
navigation regardless if they have guidebooks, maps, a compass, or anything
else.  They are neither skilled nor interested:  They most often hike with a
group and they just follow others when a navigation decision is made.  Like
most things on the trail that’s a personal choice carrying certain rewards
and risks.



Because I most often hike alone I must be responsible for my own navigation.
I carry a modest compass, a GPS, and HalfMile’s fine maps, but I use a
light, basic Garmin Geko-200 GPS rather than one of the slick, new color
mapping models.  As an ultra-lite hiker I like the fact that the Geko is
half the weight – or less – of most of the fancier models.  As a cheapskate
I like the fact that the Geko costs about 1/3 of what the fancy models cost.
In fact, I have two Gekos and I can – but don’t – carry both of them for
security and the result is lighter and less costly than one of the more
“standard” models.  If one of the Gekos went belly-up I’d still be
navigating.



I don’t use a “mapping” GPS.  I find the image is too small to satisfy me,
and I will always have the paper maps anyway.  Some say the larger models
are more accurate by virtue of their larger, more sensitive, antennas.  Maybe…
possibly… but I seldom even turn the thing on, and whenever I have it’s
never failed to satisfactorily solve my location.


In terms of accuracy, GPS locations are several orders of magnitude better
than compass-based locations.  When I hear someone criticize GPS accuracy
I’m led to believe that they’ve never tried to locate their position on a
topo’ map by triangulating from the peaks of surrounding mountains --
assuming they can actually see peaks; assuming they know for sure which
peaks they’re looking at; and assuming they can identify which of the many
bumps on the ridge is actually the peak.  It’s particularly difficult in the
Sierras where there are many peaks all strung together on ridges, but it’s a
bit easier in the Pacific NW where the tall volcanoes usually stand
prominent and alone.  There the problem is the peaks are mostly in a
north-south line and it’s hard to get something at 90 degs. to form a
triangle.


My little Gekos have limited memory so I can’t store all of HalfMile’s
waypoints, but I don’t need all the waypoints.  I look at the list and only
select important ones for upload to the GPS.  I load certain trail
junctions, road crossings, water sources, towns, etc.  The remainder of the
waypoints are printed tight, small, and double-sided for a resupply section,
and are available for me to manually enter selected locations that I may
want.  For example, last year approaching the Devil’s Slide Trail there was
snowpack for the last mile and hiker tracks were going every-which-way from
people trying to find the trail.  I could have spent the time puzzling-out
the trail location, but instead I started the GPS, selected “go-to” the
trail junction, and I walked straight to it.  After all, there was pizza and
beer waiting in Idyllwild.  While in town I spent a few minutes entering
additional waypoints into the GPS from the paper list to help along Fuller
Ridge.  As it turned out, I didn’t really need them but I was glad I had
them.


Steel-Eye

Hiking the Pct since before it was the PCT – 1965

http://www.trailjournals.com/steel-eye

http://www.trailjournals.com/SteelEye09


On Thu, May 20, 2010 at 5:34 AM, Halfmile <list at lon.net> wrote:

> For most hikers I recommend either a Garmin Dakota 20 or a Garmin
> eTrex Vista HCx. You will probably also want to purchase a 4 GB
> microSD card and the Garmin TOPO U.S. 24K West DVD. Get the DVD don't
> buy the maps preloaded on a card.
>
> The Dakota 20 is a newer model and has the capacity to store large
> amounts of track data. The Vista HCx can only store a limited amount
> of track data. Both can hold an almost unlimited number of waypoints
> if you load them as custom points of interest.
>
> Despite some of the previous posts here, these are very accurate; much
> more accurate than any paper or digital map. The PCT is not always
> accurately shown on maps, so I recommend loading waypoints and tracks
> from my web site.
> http://www.pctmap.net/download/
>
> Hikers might want to consider two other GPS models.
>
> The amazingly small Garmin Foretrex 401 weighs only 2.3 ounces (w/
> lithium batteries) yet is a surprisingly good GPS that might appeal to
> some lightweight hikers. This GPS does not have the capability to show
> maps and has limited waypoint and track storage capacity; but it can
> hold 500 waypoints and 10 somewhat course tracks so it should be
> possible to preload it with maybe 500 miles of PCT data. You can
> always use UTM coordinates assuming the maps you carry have UTM grids.
> The Foretrex is lacking some of the features of the models above (like
> maps) so it's not for everyone, but for a section hiker or someone who
> is bouncing a small netbook computer up the trail, the tiny Foretex
> 401 is a powerful navigation tool in a very tiny package, especially
> when used with my maps.
>
> I personally usually carry a Garmin GPSMap 60CSx for my trail mapping
> project. This is an excellent gps although it is slightly larger and
> for that reason I recommend the Dakota and Vista for most hikers. It’s
> great for trail logging however.
>
> -Halfmile
>
>
>
>
> >
> > Dear Eric or anyone,
> >
> > I just join this e-list.  Which GPS do you recommend?  I am heading out
> on
> > the JMT June 20th and I'm concerned about all the snow covering the
> trails
> > to the high passes and peaks.
> >
> > Melanie
> >
> _______________________________________________
> Pct-l mailing list
> Pct-l at backcountry.net
> To unsubcribe, or change options visit:
> http://mailman.backcountry.net/mailman/listinfo/pct-l
>
> List Archives:
> http://mailman.backcountry.net/pipermail/pct-l/
>