Geocaching Revisited

Hunting for hidden treasures.

Back in 2005, I discovered geocaching, an outdoor activity where people use a GPS to find hidden containers of trinkets. I wrote about my thoughts on the topic — and some big plans that never came to fruition — in some detail here. Because part of the game is to pull something out of a cache and replace it with something else, I started gathering items to share. Among these were some “travel bugs,” which are basically serial numbered tags you can affix to an item so it can be tracked. The tracking is mostly done on the Geocaching.com Web site. That’s also were you can find a list of geocaches just about anywhere in the U.S.

And that’s the interesting thing: these things are everywhere. Did you drive more than 10 miles to work today? I bet you passed at least a dozen of them within 3 miles of your car. There’s one a block from my house in Wickenburg and one 4/10 of a mile from my RV here in Quincy. As this map shows, they’re all over the place:

Geocaches Near Me
My RV is just about dead-center in this map. The little box and question mark icons indicate geocaches in the area. The smiley face icon is a geocache I found that I logged.

For some reason, I find the proliferation of these little boxes of hidden “treasure” fascinating. It emphasizes how big the world really is. It also reminds me a bit of a walk my husband, Mike, and I had along the rim of the Grand Canyon once. We got off the beaten path and walked right along the rim, far from where the tourists wander. We happened to stop for a rest on a rock outcropping. And there, tucked under an overhang with a beautiful view of the canyon, was an urn of cremated remains. How long had it been hidden there? We didn’t know. It was like an uncharted geocache. Seems like a good final resting place to me.

Geocaches are hidden. They’re tucked away in painted coffee cans, sealed lengths of black PVC pipe, and plastic Tylenol bottles. In the old days, ammo cans were popular, but I think the value of these has prevented their widespread use — too likely to be stolen if found. (I bought 3 nice-sized ammo cans from a seller in Beatty, NV some years back to create my own geocaches; I still have them.) Caches are hidden in bushes, under rocks, and among the remains of pioneer trash heaps. You’re not likely to stumble upon any of them by accident. You have to look for them. And even with GPS coordinates, they’re not always easy to find.

For some reason, I brought my bag of geocache goodies along with me on my trip to Washington this year. I guess I thought I’d try it again. I didn’t think much of it until the other day when a Twitter friend, @PlagiarismToday, started tweeting about his weekend geocaching activities. It got me thinking about it. I pulled out my bag and took a look inside it. I had a GPS with me, and an Internet connection to get information about local caches, so I had everything I needed to try again.

So I went out yesterday to search for three caches. I found three, but not the original three I’d set out to find.

  • Ryann’s Hide was the first cache I’d hunted for in over 5 years. Although I’m using a newer GPS (a Garmin GPSMap 60c) than I did in 2005, I soon realized that precision was something that needed patience. As I walked, the GPS would guide me, but I quickly overshot the location. Seems that the GPS could not keep up with my movement. I needed to slow down and let the signals catch up. Zooming in on the map gave me ever-increasing detail. Standing still, gave me ever-increasing precision. Once I caught on, I was able to zero in on the location. The cache was alongside a two-track road that led down a hill to a fishing spot. The road was closed to unauthorized vehicles. It started on the edge of an orchard and curved down into a very pleasant wooded area. (I think I need to explore further down that trail.) The container was a painted coffee can with a plastic lid. I pulled out a plastic car and replaced it with a tiny stuffed teddy bear. I entered my Geocaching.com user name in the log book, closed everything back up, and replaced it exactly where I’d found it. Success!
  • Quincy Valley Rest Area II was a bit easier to find — once I got on the correct side of the rest area fence. It was a nicely made cache container consisting of a short length of black PVC pipe with a screw-top on one end. Inside was a baggie with the logbook, some plastic dinosaurs, and a very nice shell. I took the shell and replaced it with an emery board with advertising for a nudist colony on it. (I really don’t remember where I got such a thing, but it is pretty funny — and clean.) I logged my visit and closed it all back up. Success!
  • West Bar Overlook is the one I really wanted to find. It’s located on Babcock Bench, high above one of the orchards I dried several times this summer. The entry on Geocaching.com provided lots of photos and information about the geologic significance of the spot. I’d brought along my camera, planning to get some shots from its perfect vantage point. Unfortunately, the two-track access road that appeared to link the cache area with pavement was inaccessible. Not only was there a locked gate across the road, but there were lots of tall weeds making the start of the trail a bit questionable for someone wearing shorts during snake and tick season. I’ll either try again next spring, before the weeds grow so tall or possibly try to visit via helicopter. I already scouted the power lines in the area. So this was a failure.
  • Rust Everywhere was my consolation prize. I’d already imported its GPS coordinates into my GPS, so I knew approximately where it was. But because I hadn’t planned to look for it, I didn’t have the details — like a basic description of what it looked like. Having a location but no description makes things a bit tougher. Patience and perseverance paid off, though. The cache was a label-less Tylenol bottle hidden well among rocks. I pulled out a kid’s hair clip and replaced it with a computer chip, logged my visit, and put it back. Success!

In all, it was a nice way to spend the afternoon. I was at it for about two hours and it got me out and about. To onlookers, I must have looked pretty silly, walking around while studying a GPS. But I got to find a neat place — that wooded trail — and get some exercise and fresh air. I hope to do more tomorrow.

I also think that it would be a great family or small group activity. A way to combine socialization with exercise. Working together to complete a challenging task.

I do have a geocaching project lined up. I’m going to release one of my travel bugs into the wild with the mission of traveling down to New Orleans, LA. That’s where @PlagiarismToday lives and does his geocaching. He, in turn, is going to send one my way. We’ll see which one completes its mission first.

I’ll likely blog about the progress here.

The Big Detour Map

Annotated map to my most recent flight around the Cascades.

I wrote about my long flight around the Cascades here; this sectional chart shows the actual route with points of interest. You can click the map to get a larger view without the annotation letters.

Big Detour Map

A – Starting point in Auburn, WA, a suburb of Seattle.
B – The first canyon I attempted to fly though. I climbed above the clouds when I turned around to backtrack.
C – My first descent back below the clouds.
D – Where I hooked up with Route 12.
E – My big scare in the clouds. I was less than 5 miles from the pass.
F – The ridge I crossed to descend to the Columbia River Gorge area.
G – The Dalles, where I refueled.
H – Skirting around very low clouds.
I – Skirting around a restricted area.
J – Mattawa, where I had lunch with a friend.
K – Quincy, where the helicopter is based for my first contracts.

In the 3-1/2 hours I flew that day, I could have been 1/3 of the way back to Arizona.

E25 to BFI by Helicopter on Google Earth

My four-day trip, plotted.

I’m a geek. Everyone should know that. This just proves it again.

I use a gps logger to track my GPS coordinates when I’m out and about taking photos, mostly so I can geotag my photos. But on long flights, I often turn the GPS logger on and let it collect my coordinates as I fly. The logger I use has a huge memory and was actually able to accumulate GPS coordinates for my entire helicopter flight from Wickenburg, AZ to Seattle, WA.

Helicopter Flight on Google EarthThe image shown here shows the four days of my flight. Day 1 was Wickenburg to Page, AZ. Day 2 was a photo flight on Lake Powell followed by a flight from Page, AZ to Bryce Canyon, UT. Day 3 was Bryce Canyon, UT to Salt Lake City, UT and then on to Yakima, WA. Day 4 was a bit of scud running to get to the other side of the Cascade Mountains, from Yakima to Seattle, WA.

If you’d like to look at the track points in detail on your copy of Google Earth, you can download them. They show altitude, too, so you can get an idea of how high or low we were for various stages of the flight. You can probably even do some kind of flyby if you have the right software.

Pretty cool, no?