Lemon Fresh Dog

Looks similar -- I notice one of the caches indicates that the coordinates are incorrect. (although it took a little looking). I assume they could be updated to the correct coordinates at any time.

Okay -- cool. That makes sense because I also have 7 travel bugs and 11 Canadian GeoCoins to place into these caches (plus some unactivated ones that may start their life in these). I guess I could throw them off a few hundred feet -- warn the players in the description and then give the accurate location in the "multi" and update to true accurate locations after the last of the 18 racers are through. (allowing future generations to enjoy them as traditionals)

I guess I can devulge a little. The first cache is where it should be -- easy to find (well...) and traditional. The players all "arrive" at the cache, get "outfitted" for the "journey" and are given the REAL coordinates of the second cache. They visit the second cache, grab another "element", sign log, trade, etc and get the coordinates for the 3rd cache to move along. As soon as they reach cache #7, they have all elements needed and are directed to the 8th and final treasure cache. Of course, I've created treasure all along the route, plus logbooks which I would like signed physically and online. If there is an approver in the house, or someone that has done this. Would it be considered "good form" to do the following: 1st Cache -- approved where it is, true coordinates given 2nd -- coordinates in the middle of an Ocean. Real Coordinates supplied to approver, coordinates updated to the real ones at the end of the 18th player. 3rd - 8th -- same as #2 above Obviously, by placing the coordinates in the middle of the ocean somewhere, it won't get people looking for it there. However, I also know there is a limitation on how far a cache owner can adjust coordinates after approval -- so this mean the approver would need to approve the update (of course, they could have the real ones at the onset)

Here's a challenge I am having...can anyone assist w/suggestions? I have an 8-container multi that I am placing. It consists of 8 medium cache containers all stuffed with goodies and logs and pencils etc, etc. It also contains a series of "game pieces" For the first 18 people, there are game pieces to collect, assemble and "X" to the next cache. As these folks complete each cache they are directed the next cache, next cache.... and then to the final 8th cache. Okay -- it's a multi of traditional caches. good. However, what I would like to be able to do is have cache pages for each "stage" so that each stage visit is logged and then, after my first 18 racers are done, have these all revert to traditionals that can be searched in any order by regular cachers. (the game pieces are unique and this is a one-time race) Can anyone assist on the mechanics of this? If I list all 8 caches they all appear -- people can skip stages and the order intended If I only list one, there is no place to log the stage visits or keep the visits after they go traditional Should I list real coordinates for the 1st and then "fakes" for the 7 with **CACHE NOT HERE** and then update the coords after the 18th player passes through? If so, am I causing other cachers harm in placing by taking coords that arent there? Can an approver place 8 caches at the same coordinates to start? Then, modify at the end of the game to the real locations? long post - sorry.

That was just ugly. I'm glad I was able to contribute before the plug got pulled -- I know there are many good charitable organizations -- I try to donate to the United Way to cover them during the year. This was a one-time event that killed 155,000 people in less than a couple of hours and is a "special event" when it comes to giving. I'm sorry that the "me too" scenario led us to the lowest common demoninator -- and end to the cache. We all lose so that no one loses -- been there before. I totally understand Groundspeak's position on this. I'm just a little sad we couldn't have all looked the other way on this one. Rules are rules.

I'm glad you caught a faker -- kinda fun and a little sad (but only a little) It's actually inspired me to create a series of caches called "Find the Fake" -- in this series, the cacher must visit four locations and take their picture at each -- BUT -- ONE of the locations has to be a faked photo! Then, others vote on which of the four is faked for the "finders". The finder with the least fakes found wins!

As promised. I'm closing the thread -- thanks to folks that responded -- it was intelligent and civil -- how very happy I am!

I'm about 80Km in radius -- most are less than 2KM from home or work. I plan a series of caches that are almost 1000KM away, but they are remote and I visist at least once, if not 2-3 times a year, so I hope to get them approved basaed upon my commitment to maintain them. I also have back-up maintenance "staff" in the areas of my planned remotes.

I like the way it reads. Seems to give people something to follow as they enter the game. Of course, one always has to worry that it could become a crutch or a bat, but I think most reasonable folks could live by such a open, yet functional creed. I suspect many follow the practices outlined within it already. I like it. Maybe don't need it, but I like it. edited for spelink

Here are some of mine: Geocaching Patches Unregistered Travel Bugs Logic Board Game (new) Coffee Shop Certificates (Starbucks Cards) -- I sometimes "sneak" these into caches as a "next to find prize" I like to try and "theme" them as well. Can you guess which one above was for the "Coffee Cache"? I'd really like to create a signature item sometime.

My favourite trade item is a good story. I really enjoy reading about interesting experiences people had at the cache, avoiding onlookers, or just seeing a view I thought they might enjoy. I stick a bunch of stuff in there too -- ussually $2-$5 items from a local dollar store. Some kids toys, some trail tools -- that sort of stuff. Primarily on the 1/1 caches that I am more likely to be serving to children. I'm also thinking of placing geocaching stuff like T-Shirts, patches, unactivated Travel Bugs on some of the 3/3 to 5/5 caches that I am planning or as part of multi-stage treasure hunts. I also visit the caches at least once every 6 months (more in the summer, less in the winter) to re-stock and clean them up a little. Which if probably why I am not too concerned about what people put in, but don't want them to just take. (TS LN SL) --- grrrrr. (ah... who am I kidding, if someone REALLY wants something, go for it) Overall -- something for everyone. I don't much care for TNLNSL all alone as an entry, but that isn't for me to decide. Maybe the person was in a hurry, someone was coming down the path, they didn't have much to say -- that's okay. I do agree that if that was exclusively what people wrote then I would likely stop placing caches because the feedback would be pretty dull. Seems there's something here for everyone to enjoy.

I just downloaded it and will play around to see how it works. Thanks!

Great! Thanks -- I'll go play with that. I'll close the post now.

Yup -- there are some nasty things in the woods. One of my caches was found with syringes near it, so I had to disable and move it. The best bet is to exercise caution -- when in doubt, don't touch it. My biggest fear is not the garbage of the users and makers, but coming across active grow operations in the deep woods off logging roads. If you find yourself surrounded by tomato plants without tomatos on them -- get out! (I suppose you *could* fill a CITO bag, but I wouldn't recommend it)

Are there any plans to allow Premium members to connect to the Geocaching website and pull cache data as XML? This would allow us to write our own databases of caches based on a wider range of filters. I like Pocket Queries and MobiPocket -- maybe I just need to play with those more.

I'm sure this has been asked, but I cannot find it. How do I filter caches in my area to see ones that currently have travel bugs in them? Or at least a "last seen in" criteria? I want to see if there are any local cahces with bugs or the potentail for bugs. Can this be done short of searching all caches?

Sounds good. I'll chalk it up to an idea that had no home! Thanks for the feedback on the thought though -- and THANK YOU especially for not turning this into a rant on cache maintenace! I do like the idea of the owners last visit on the cache page as I am currently writing a Geocaching PocketPC application as a way to practice my .NET Compact Framework Skills and this would be a neat item to pull. (some things CAN be solved programmatically -- just not very important things ) Unless there is something else, I'll close this thread tonight or tommorrow to keep things tidy.

That's a neat idea -- I sort of like the idea of a rating system by users -- but maybe that's another discussion? Don't know. For the two of you that have answered "no" -- is that a "no - please don't" or a "no - not for me". Is it something that would bother you, or something that you just don't care for? I mean that in a sincere manner -- sometimes with only text it could come across the wrong way -- so I'm just asking, not challenging the "no" in any way.

Hello all, It seems we're starting to get into the territory of some threads that have been discussed. Is there still value to continue this thread? I'll leave it open, but if anyone flags a "been here, done this" I'm okay to close it. Just let me know. The main question I was interested in was whether some sort of feature would automate cache health checks. Not really as a way to see what shape they are in, but rather as a way to see if someone was still taking responsibility for them in the event they entered a state of disrepair, needed to be (re)moved, or are gone altogether. I'm assuming that if someone is concerned enough to raise their hand and say "I'll take care of that cache" then it will be in some state of "maintained" <--- whatever that may be. I normally read all the logs -- so DNF's work for me. The challenges that has been brought to my attention is that some folks do not read the logs, or do not log DNF's, or that some caches are simply very hard to find. Another thought I have seen is the use of the SBA flag -- but this has been discussed quite passionately elsewhere. One solution being a new status proposal: SBC (should be checked) or the like. That's another conversation though and somewhat divided. I'd rather not place that into this thread if that's okay, because my objective is to look at cache-owner/care-taker responsibility rather than players. I'm thinking maybe a poll would be in order? The proposed question being: "Would you like to see a feature implimented that indicates the last time a cache owner visited their cache page?" Although not perfect, this would be a non-issue to folks that don't care, but provide an additional decision criteria for those seeking caches to use as they see fit? Although some owners do not visit their cache page often, it would not exclude the cahce, but act as a slight indicator to the seekers that the cache has a higher probability of being in place. Thank you to everyone for keeping on topic -- I am very impressed we haven't started taking sides on this and are rather discussing pros and cons of a process. (note: my personal bias is to have an informational flag -- I just don't know if I'm completely out-to-lunch in asking for this. My objective is to be able to create a filter of "high-probable finds" and "questionable"/possibly missing finds. Visit type A with my daughter and type B as time permits.)

You know what -- you are right. Absolutely correct. Thank you for the perspective. -- I have donated $100 to the Red Cross Relief effort for Tsunami victims. Our government is matching donations. I'm serious. Thanks for the reality check.

It's good to hear from folks with so many caches -- I guess that would be a hassle to have to manage. I guess the core of what I'm intereted in is some sort of informational flag to let me know if a cache is worth checking on. I read the logs so I'm ussually not in trouble at all. As a cache owner I was thinking about how I might better serve those seeking my caches.

I also apologize for my participation in this offensive thread.

You don't advocate trading, but leave the option open. I suggest it is not optional. Again. Do not call me a lier.

Hmmmmm..... those are all good point too. You know, I'm thinking that maybe what I have previously read about un-maintained caches is actually the exception rather than the norm. I know that in my neck of the woods everything seems to be just fine. Maybe the best post above is the "I like things the way they are" ???

That's a great solution Jeremy. My objective is just to know what caches are "healthy" the "watering" idea is perfect to this objective.