ADKer

The OP was taking about cache adoption. Dame Deco went on to say if we save all "good" caches, we won't have any new ones, which seems counter-intuitive. Archiving (not adopting out) a "good" cache for a chance that another "good" cache replaces it seems like a losing proposition. I certainly agree that it does happen, but much more rarely than the opposite. As for a cache deteriating over time sure, but it then its likley not a "good" cache anymore... Maybe we need a clearer definition of what the OP means by a good cache. The cache owners I know that put out good creativity, skilled caches (often requiring craftsman type work) often don't archive them until there's a problem - the cache has deteriorated and can't be replicated, the cache went missing, someone smashed the cache and it's too much work to replace it. All very legitimate reasons to archive. If they put those caches up for adoption the adopter would likely replace them with something different, which changes the cache. So what's being saved? The GC #. My definition is irrelevant. The entire process form posting the log to adopting the cache would involve both the CO thinking their cache is good enough to save, and some other cacher thinking it's good enough to save. Also, if one of my cache containers disappears or needs to be replaced, I'll put a new container in the same spot. Sure it's technically an entirely different cache, but I don't archive it. Would this be possible?; How about an option for the CO to change the cache type icon to an up for adoption specific icon that populates on the map? Both are possible, however I think your idea may be harder to implement. Yes, that occurred to me too. I think it would get more exposure though. Like others commented, unless the cache in question was bookmarked on a list, a cacher may never see the Up For Adoption log. It would pop up on the map as a unique icon though. At least until the user hides icons... Just a thought. Implementation would be a bear compared to a log type option though. Bookmarked...or they set their instant notifications for this new log type. That is what my whole plan is based on.

The OP was taking about cache adoption. Dame Deco went on to say if we save all "good" caches, we won't have any new ones, which seems counter-intuitive. Archiving (not adopting out) a "good" cache for a chance that another "good" cache replaces it seems like a losing proposition. I certainly agree that it does happen, but much more rarely than the opposite. As for a cache deteriating over time sure, but it then its likley not a "good" cache anymore... Maybe we need a clearer definition of what the OP means by a good cache. The cache owners I know that put out good creativity, skilled caches (often requiring craftsman type work) often don't archive them until there's a problem - the cache has deteriorated and can't be replicated, the cache went missing, someone smashed the cache and it's too much work to replace it. All very legitimate reasons to archive. If they put those caches up for adoption the adopter would likely replace them with something different, which changes the cache. So what's being saved? The GC #. My definition is irrelevant. The entire process form posting the log to adopting the cache would involve both the CO thinking their cache is good enough to save, and some other cacher thinking it's good enough to save. Also, if one of my cache containers disappears or needs to be replaced, I'll put a new container in the same spot. Sure it's technically an entirely different cache, but I don't archive it. Would this be possible?; How about an option for the CO to change the cache type icon to an up for adoption specific icon that populates on the map? Both are possible, however I think your idea may be harder to implement. I see no problem with the local caching community keeping alive classic caches...in some cases CO's die. Too true, and those are the ones I think ADKer is talking about. I agree with Dame though; there are plenty of caches in my neck of the woods that would be better off dead and gone. Yes. The idea of my system would be that caches aren't forced to be adopted. It would simply better allow the community to save the ones that they think are special.

Does this feel like an off topic thread to anyone else?

The OP was taking about cache adoption. Dame Deco went on to say if we save all "good" caches, we won't have any new ones, which seems counter-intuitive. Archiving (not adopting out) a "good" cache for a chance that another "good" cache replaces it seems like a losing proposition. I certainly agree that it does happen, but much more rarely than the opposite. As for a cache deteriating over time sure, but it then its likley not a "good" cache anymore... Maybe we need a clearer definition of what the OP means by a good cache. The cache owners I know that put out good creativity, skilled caches (often requiring craftsman type work) often don't archive them until there's a problem - the cache has deteriorated and can't be replicated, the cache went missing, someone smashed the cache and it's too much work to replace it. All very legitimate reasons to archive. If they put those caches up for adoption the adopter would likely replace them with something different, which changes the cache. So what's being saved? The GC #. My definition is irrelevant. The entire process form posting the log to adopting the cache would involve both the CO thinking their cache is good enough to save, and some other cacher thinking it's good enough to save. Also, if one of my cache containers disappears or needs to be replaced, I'll put a new container in the same spot. Sure it's technically an entirely different cache, but I don't archive it.

Ok, lots of talk, so I won't quote any text here... Anyway, firstly the "Up for adoption" log would be set by the Cache Owner. The cache owner would have to acknowledge that his cache is worth saving and hope that someone else agrees. Next, someone would have to contact the CO to begin the adoption process. If nobody thinks the cache is worth saving, no one will bother. All of that will take place as apposed to archiving the cache not after. All this log would be is a flag that is put up, letting cachers know that the owner wants to adopt it out. It wouldn't change the current adoption process at all. Also, someone mentioned that a person would have to have the cache on a bookmark or watchlist for the log to be any use. Well...no. What makes this log any use at all is that it could show up in instant notifications. There are plenty of caches that I would be willing to adopt around here, but I don't add them all to my watchlist. Oh, and one more thing. This log wouldn't be mandatory for getting the cache adopted. If somebody has a friend that they'd like to give the cache to, they could do so just as they can now. Ugh...I had more things to say, but now I forget...

If I'm just getting a quick cache in town I'll use my android. Otherwise I prefer my eTrex 20.

And I'll never even get a chance to find the cache!

I wish there was a way to view the DNFs of someone. Here's one of mine: Here's another one, between my two logs, the owner updated the coords, but deleted it after my FTF.

They also would see those types of logs if they've included "Up for Adoption" type logs in their notifications. Yes! This is what I was imagining when I thought there should be a separate cache log type. Something that people could watch out for. Also, as others had said, yes this would still take some positive action on the old CO's part. This would help stop every single LPC/Micro in the woods/very generic Tupperware cache from being saved from archival.

It sounded to me like the OP was just suggesting an additional log type (with a unique icon) as as way to "advertise" that a cache is up for adoption. It wouldn't eliminate any person-to-person communication. In fact, the CO putting the cache up for adoption may decide that the first person to answer the "ad" has a poor cache maintenance record and decide that they'd prefer someone else adopt it. A "up for adoption log" doesn't prevent a CO from posting a note on FB or local cache group mailing list as well. Some caches are not worth keeping. Some are not even worth being replaced. However, some *are* worth saving. An "up for adoption log" wouldn't change that. Thanks, I couldn't have explained it any better myself!

That's definitely OK! The rule is equal or greater, so if you taking nothing, you can leave anything greater than nothing! Oh, P.S. Welcome to geocaching!

Crowd psychology and mesmerizing quote trees. The scenario is more addictive than crack! It's like getting drawn into a black hole. There is no force to stop. You still have at least 10 more posts to go before you win the thread. Someone must have hacked my account! Well Dude, you shouldn't have used Geocaching as your password. Hey, is this quote tree getting long enough for you? It's not even halfway to the limit. Getting there. And my password was more clever than "geocaching." I went with "p-a-s-s-w-o-r-d." Tricky, huh?! Not as bad as 12345678. Yeah, at least I added a 9 to the end of that.

I agree that that is probably the best way, but in certain areas (The Adirondack Mountains) there is no local facebook/organization, and that makes it much harder to do what you're suggesting.

Well, I figured that it wouldn't have to be adopted. If no one shows interest (such as an LPC), then the owner would archive it. (Or the log is treated the same as a NA and the reviewer would come to archive it?) Also, this wouldn't be affecting the adoption process at all the way I'm picturing it. To adopt it, a cacher would have to contact the CO and the normal process would take over. This new log would just be a method of saying "hey, does anybody out there want to take over this cache for me? I hate to see it go, but I can no longer maintain it for whatever reason."

This one's fairly simple. Owners of a cache would be able to make a type of log called "Up for Adoption." The reason that this would be beneficial is because people could set their instant notifications up to alert them if a cache owner no longer wants to look after his/her cache. A nearby cache that was in excellent condition was just archived today because the owner was "quitting" geocahing. The cache was one of the oldest in the county, over 13 years. Anyway, this log would give caches to be adopted out, instead of just archived. Just a though. Any ideas?

OK. Firstly, to get geocaches: You must download the GPX file or pocket query to you computer. (I'll assume you know how to do that, if not just ask.) If you get a pocket query, unzip it. Then move the .gpx to the eTrex. Put it in the "GPX" folder, which in turn is inside the "Garmin" folder. They should now appear on your eTrex. Next, to enter a coordinate, there are two ways. If you are already navigating to a geocache, go to the "Geocaches" tile on the main menu. Scroll down to "Enter Next Stage" and click that with the joystick. You should now have a screen to input new coords. Now for the maps. The GPS comes with a very poor basemap. To get any real use, you'll have to get another map. I recommend Open Street Map. There is a link up above to the site. Again, once you download that, put it in the "Garmin" folder. I hope I did a clear job at explaining. If you have any more questions, just ask!

On the souvenirs page, under each souvenir, it says the date that it was acquired on. This text should be a link to the log that the user made that gave them the souvenir. Any thoughts?

Sign up Roman! His main goal is to save unnecssary work, which includes actually seeking caches. Absolutely not true, there is no rule you have to solve a puzzle, there is a rule you have to sign the cache, my suggestion breaks no rules, yours does. According to the Terms of Use, no one is allowed to: So yes, it is breaking a rule. And I doubt many puzzle owners would give consent.

OK, here's what I have so far. It definitely needs a lot of work. I tried to make it look like the classic tennis serve. I need to fix the racquet's shape, and there's something not right with the left leg (our left). I'm also thinking of making the right arm a bit longer. Any other suggestions?

Awesome link. Thanks! It wouldn't fall under "impersonating a lackey" if I were to make one for myself, would it?

Wait... this was a serious thread?

I've been curious as to how the avatars that some of the lackeys and waymarkers have are made. You know, those pixel ones, such as these or these. Is there some program that designs them, or are they all done by hand? What's up, does anyone know?

Read the manual then you can ask specific questions that we can answer. There should be a PDF copy on the GPS but if not you can find one at Garmin.com. In case you're as lazy as I am, here's the link: Garmin eTrex 10 Careful though, it also has features only located on the 20 and 30.

It's a new product by Goodyear, I just bought 7!

I'm not German. Well there's your first problem.