More Road Trip Cache Planning

I've offered some suggestions in the past about how to go about setting up for a trip that involves geocaching; either as the focus of the trip, or as a diversion from the real purpose of your trip. Now if you are one of those cachers that uses one of those newfangled wireless devices like an iPhone or an Oregon or anything that doesn't require uploading pocket queries onto your GPS receiver, then stop reading right now because this post doesn't apply to you. For you old school cachers like me that will never part with your Garmin GPSmap 60Csx or eTrex, then read on.

What happens when your trip is so long that you find it difficult to load all the possible caches along your route on to your GPSr device, whether that limit is 500 or 1,000 waypoints? I had that experience recently when planning for a college road trip with my daughter, which took us over 600 miles one-way from the San Francisco Bay Area to the northern reaches of the state of Oregon. My GPSr holds 1,000 waypoints, so I needed to set up my "caches along a route" pocket query with a small enough search radius to accommodate as many caches as I could fit. I split the trip into two halves of about 500 caches each, and it turned out I needed to limit the search radius (distance from the route (Interstate-5)) to a quarter-mile along each side of the highway:

That's much smaller than I generally like to use, but that's the best I could do. I also needed to add a limited number of caches from the college towns we were visiting as well. After loading all my trip pocket queries into GSAK, I had well over 1,000 caches; about 1,300 in fact. So now what? I couldn't just start deleting caches indiscriminately to get down to the magic number of 1,000 caches.

The trick I like to use in this situation is to employ the "Last found date" filter in GSAK. I set it up to show me all the caches in my Oregon trip database that have not been found for the last 60 days, figuring these caches have either already gone missing, or were too difficult to spend a tremendous amount of time messing with on this trip:

You can set the number of days to whatever suits you, but it turned out that 60 days was perfect in this case, as after deleting all of the caches in this filter, I got my list down to 994. Perfect!

Something to keep in mind when you find yourself bumping up against your GPSr's waypoint limit.

Cache On!