I’ll third that

@PCFrog wrote:

: So, my main question is do people do this on purpose or is there some other reason that escapes me?

I think the answer is simple. Maybe they just never thought of it from your point of view. The GPS thing I mean.

I have a series, well, down to just one cache left in it now, that is called “Little Know Parks: Name of Park”. It was one of my first series of caches, but the thought never crossed my mind that this wouldn’t fit in a GPS, simply because most folks around here either cache by the GC number, or do like I do, and change the name manually so it’s easy to remember.

We can’t always anticipate everyones needs and wants when placing a cache. Try to keep that in mind eh? 😀

Ok, let me just bring up this point, which I discussed with Marc on the whole WSQ naming thing but I’ll throw it out to everyone here…

If the whole purpose here is to make it easy for those 6 or 8-character GPSers to use, why not just use the handy gc number that is already there?

Not to go off topic, but I did notice that CacheMagnet for the I-pod does both, name & GC#.

I’m sure those that have an issue with long cache naming conventions have a lot to say about S|S caches. The vast majority of mine are 2-Part names. The first part giving the cache a category that places it in a certain series or class of hide and the second part being specific to the cache itself. If I employed the suggested acronyms, I’d probably drive myself nuts trying to remember what they all stood for.

The one thing I have going for me is that 100 of the 166 I own are puzzles and very few of them are field solvable, which means you are simply not going to be going to the cache before you have a solve in hand, on paper most likely, and therefore this is a non-issue.

I do understand the frustration some of you must feel with the limits placed on you by the devices you use and apologize it this leads to frustrations when hunting any of my caches. But, I have come to embrace my naming convention and it does help me keep track of my own caches. Anyone with a hundred plus caches knows how difficult it can be to remember what the cache hide is on a specific cache. I don’t know how Marc can keep all of his WSQ caches straight, especially when some of them have the same cemetery name – I guess that’s why he recently amended his list to include the closest town.

It just goes to show you that you cannot please absolutely everyone in this sport and each of us runs into our own limitations with equipment and software depending on what we decide to use.

And from the ranks of the archaic, as Giz puts it, an answer to the last three posts. Papyrus. Yep, I use a 100 and 210 and a few maps with cache positions and hints. Sometimes I’m lazy and print up a few cache sheets too, especially if the cache is a “complicated” puzzle or earthcache. I guess I’m trying to support the local paper industry while I continue a long-delayed transition to paperless. After a couple thousand caches I have a nice chronological quasi-scrapbook of solves and finds. Takes up space for a few books on the bookshelf, but when I get a call from someone who likes the PAF method of making a find, I can retrieve what they need in under sixty seconds. Sure I take a little heat from my peers on my ancient mariner methodology, but there’s nothing like a good map with topographical features when it comes to going out in the sticks. Otherwise I just remember the street names around town and the other places I go. Even have a photo of Marc carefully looking over one of my archaic accessories on a recent trip, though I don’t think I going to get him hooked on paper. Comes in handy when a log is full and you don’t have any spares in the pack. Not for everyone, but works for me and I sure do like the routing I create in advance.

@Cachelovskys wrote:

As long as we are venting on this issue. My problem with my GPS (eXplorist 210…I know, but it still finds caches) is that if two or more caches have basically the same name (for example, another walk in the park 1 through 4327), then it automatically deletes all but one, because it thinks it is a duplicate.

Does anyone know how to fix this? a solution that doesn’t cost money?

I don’t know if I ever noticed this problem on the 210, are you loading using the Magellan geocache manager software or GSAK?