BlueDeuce

I don't know. I guess I could consider it a possible maybe but really you aren't going to get that many people to use the option. At least not enough that you can avoid caches before you get within that last ten feet of vegetation. It's kind of the nature of the beast that geocaching is off trail. That's why I have a pair of gaiters.

A lot of good memories using the Vista. Mainly finding caches.

The Pocket Query option allows you to search by cache size. Or you could simply download all the nearby caches and use GSAK to do the filtering and even search cache names of Hotel. Motel, Lodge, etc. Personally I wouldn't put too much stock in gleaning data from the Past information. People 'visit' travelers through scores of caches regardless of anything other than that they found it. And yes I do mean just one bug.

You can revisit caches to Drop or Pick up a TB. I drive 35 miles to work everyday and I have several choice cache locations that makes it easy to help a Traveler move in one direction or the other. Go find a cache good for a TB that you trust to be away from muggles and then Move Those Bugs!

There have been a few blips along the way but honestly no, my priorities haven't changed. I do exactly what I do since the day I started.

Oh, and when kids are in school.

How old is it might be another question.

I think a lot of people just don't care. It's simple to type “took [item]” when taking some cool Swag item, yet look how empty caches get, vs. how many people admit taking something -- the value removed from the game, not moved to another cache. The reason Trackables don't get logged is that they are even more trouble to log than the Swag was. Yeah, I've never been under the impression that bugs were simply moved along and not logged properly. They are picked up out of a cache and that's it.

I give permission to anyone and everyone to pick up my bug and move it regardless of the circumstances. If you have a problem with that, go buy your own bug and tell people they can't move it.

Honestly, in this day and age hotels are the only caches people can find large enough to hold a tb and have a chance someone will pick it up. Don't get me wrong I'll take issue with take one - leave one but the fact is people find the newest caches and those are micros. We need something out there that people might be willing to revisit just to drop a bug.

Sweet. Thank you. Seriously.

Ok thanks. So, you don't have to leave a trackable for the next person but can dip it in and out of a cache and take it with you? I assume it doesn't have to physically fit - or is this what the physical dip was referring to? Rather new to all this! And the newer term is for a trackable to 'visit' a cache? For historical accuracy - Dipping is to Drop a TB into a cache listing on line and then immediately do a Retrieve. (This term was coined by a newbie several years ago) The act is perfectly acceptable as the cache may be too small to leave it in but you still want to give the TB credit for having been there. Visiting came about because Coin owners were taking albums (envision 300 coins) to events. Dipping each one to get the event location credit was too time consuming so gc.com created the visit option to give people the ability to mass-log their coins. Then there was the issue of people given a paper list of those 300 coin tracking numbers, having to Retrieve them to get credit and maybe Drop them back into the event, sometimes days later after they had been actually picked up and moved to another cache, was causing a lot of confusion. So gc.com created the discover option. And now you know why you have people discovering your TB, "just so you know it's still there" and visiting cache after cache after cache after cache after cache after cache after cache after cache after cache after cache after cache after cache after cache. after cache. bd

hmmm, I would be interested to see if Groundspeak would respond to a lock request.

Right now my adventure is to not make caching feel like a to-do list. I think there might be just enough polish on the apple to get me through the last four days.

Two issues. Your gps can only get you so close to ground zero. Once you get to the area you tend to slow down so your gps has difficulty know which way you are facing. Walk some 60 feet away and make a steady approach. Make a visual line of where your arrow is pointing. Walk away at a right angle and make another approach. Where those lines intersect is where you should start searching. Put your gps away and search a widening circle.

The history of Virtuals is most likely the problem. Give your idea a new name and it might fly.

Much better. Thank you for the update.

Clearest example of why you should really really realllly consider whether or not to purchase and release a Travel Bug. If the people you are asking for help can't explain a completely simple process and in fact degrade you for asking, there is not much hope for any TB. Dunno how you got degrading out of my comment that he shouldn't worry about it. The process was already explained, so there was no reason for me to describe it again. Furthermore, the process isn't actually simple at all, and I would suggest that it's as likely to cause new problems as to fix the rather minor glitch. You can't be bothered with it so why are you posting?

You have to take the bug to the cache and then log it through for it to get credit. That will show the mileage. As for your thief, take some time and pick up bugs and move them out. Otherwise ignore him completely. He's only doing it for the attention.

There's a local cache that has like seven containers attached to a board. It's a fun game to not have the last container chosen be the real cache.

It's certainly no worse than searching through a giant pile of rocks. Go for it. On a personal note, if you keep me searching at the back of a stuffmart I'll probably pass on it. But that's just me.

Some good news. The actual pq data that I pull and load into GSAK is correct. It appears it's just the preview option.

Right now I've got PQs giving me data 80 miles away. And it clearly says it's 80 miles from my search location. If I hit map this location it shows the right place.

Current policy is that if you purchased it you can do whatever you want with it. I would like nothing better to have gc.com prove me wrong.

First thought: Not all geocoin thieves sign the logbook. So don't assume the last logger did it. At least without more proof.