team tisri

When doing a walk that takes in multiple caches I usually print a map from the software that came with the GPS. In my case that's Garmin's software, topped up with Europe City Select for detailed street-level maps where needed. I mark the caches as waypoints, define my route between them (using straight lines rather than road-routing) and then print the map. Although my GPS will tell me which cache is nearest when I mark one as found, it might be one I'd planned to get on my way back. When you've put all the caches you'd like to find on a map you can build your route to pick off as many as seems sensible. My last proposed route was 18 miles around London taking in 34 microcaches, although in the end it took so long to fail to find the first two we didn't make it very far...

Sounds in line with what I thought. Thanks for your thoughts people!

I just started geocaching a couple of weeks back and recently picked up and moved my first TB. I notice a couple of caches seem to be known as stopping posts for TBs and wondered if it's considered bad form to revisit the same cache to take and leave TBs to help them along their journeys. Gut instinct says probably not but does seeing the same name visiting the same cache rattle cages in a big way?

I reckon more than 1 but not very many more. As soon as someone with a bit of know-how in repairs finds it then they've got a new GPS and you're down a TB. Will be interesting to see where it ends up though.

Don't forget one thing, not everyone can or does log online right away. You mention Red Rock Canyon. That's a very popular spot with tourists. As a matter of fact, I was there a few weeks ago myself. I was not able to log any of the TB's we took or left for a few days, when we got back to CT. Another cacher I met up with there had cached his way there with a camper, and then cached his way back to California again. He was on the road and without access to the internet for a week or more. I'm not saying newbies don't make a lot of the mistakes too, just pointing out that even experienced cachers can't alway log a TB in or out of a cache within hours of visiting it. If you are in a popular tourist area like Red Rocks, or if it seems like the person who dropped off or picked up a TB isn't local, cut them some slack. Check to see when they last logged into the site. If you picked up a TB that doesn't show in the cache yet, shoot them an email and wait until you hear back before grabbing the TB from them. THis is very true. On a recent holiday I went looking for TB's only to find two of them missing. The reason they were missing is that another cacher on holiday in the same area got there first, but since I didn't have internet access and I presume they didn't either, their finds didn't get logged online until they returned from holiday. Frustrating, but that's the way it goes...

As a relative newbie I think the site could do with something to make it clear how to explicitly pick up a TB. I went looking for 3 of them in Devon only finding one (another cacher beat me to the other two) and it was only by chance that I found the formal method of telling the site I'd taken the bug. Perhaps when logging the cache find the option to select which TB (if any) you took from a list would help, just as you have a list to show which TB you left behind.