This topic contains 27 replies, has 14 voices, and was last updated by 
-
Posts
-
Greetings!!
While planning for our trip to MO this weekend I spent some time looking at the caches surrounding the MOGA event. One cache in particular caught my eye and I thought that maybe we could do something similar…
The event is GCKR4A…this event will have 40+ temp finds at it (similar to our events) but the interesting part is that there is a companion cache to the event…GCAB22…It’s purpose is solely for people to log their temp finds at the end of the event!
This will allow the caches (temp or otherwise) to show up as a cache find instead of an event find!
Could this be something that we adopt for the camp-out?
I thought it was a great idea!
BillInteresting idea.
It appears that the second cache is ONLY to record the event’s temp finds (and is not a physically findable cache itself, which would serve dual purposes otherwise).IF the WGA approvers would approve of this, I think it would be nice. Will be interesting to see what they say, as this would represent approving a cache with a very short life span, that “appears” as if it was a cache that was going to stick around (ie. not an event listing).
But in my opinion, ONLY if it’s just for containing the temporary event finds, not with an “string attached” of it also being a findable cache. Because I think if it was dual purpose (ie. both temps finds and a cache itself) it would “muddy the waters” for future finders (post-event) that are looking at the log entries. Also, depending on where an event is held and how many regular caches are there already, the property managers that allowed the event may not wish to have another regular cache on their property.
The second cache is ONLY for Temps!!
Permanent ones are to be logged on their own page. Note the links that are set up to the permanent cache pages.
Given the lack of other decent options, I think it is a GREAT IDEA!!!!!!!!!!
If SLAGA can do it, WGA can and should!
I like it!!
Bec
I like it too.!! My personal opinion is if you find the temp cache that is good enough or better then a regular cache, then you should be able to log it.! You still got to find it like any other cache, so why not get credit for it..
smokey
“Be safe and Keep on Searchin”Hmmmm, very interesting
My first thought is that if it’s listed as a cache page, it must be permanent. Temp caches are not allowed to have their own cache page.
As an approver, I could easily create such a cache page for us. If I saw one of these submitted, I wouldn’t approve it. It would be double standard it we did it for our events but not others.
I’ll have to check with the other admins to see if this is now being allowed. I personally don’t have a problem with it and it seems like a good idea. It does violate the permanant cache guidelines however.
Grousetales … thanks for checking into this. If such I thing was allowed, I really think it would make sense to allow it for all events, not just official WGA events. As all events have the same issues, they are not unique to WGA official sponsored events. Just my 2 cents.
Grousetales / All … Now lets just say for a moment that this was something that any event organizer could do and would be approved … Does anybody agree with me that it would be cool and show a WGA membership consistancy if we “suggested” a cache naming structure for these special event listings? My idea that comes to mind would be “ECHO”, short for “Event Cache Hide Organizer”. As an example, the one for the event I’m co-hosting could be called “ECHO The Secrets of Stonehaven”. What do the rest of you think? Would it not be handy to know that when something starts with “ECHO ” you’d know what you got before you click on it?
[This message has been edited by EnergySaver (edited 04-06-2005).]
Well then, why not, after everyone has logged their temporary finds, just put a permanent cache in the cache log page, as a sort of memorial to an event?
(Sort of in a way like Team Badger does)
Do I make sense?
Becquote:
Originally posted by GrouseTales:
Hmmmm, very interesting
It does violate the permanant cache guidelines however.Okay…so stop and think about this for a minute…aren’t ALL events only temporary caches? So if you can approve a temporary event why not the hides involved?
I do like Bec’s idea about dropping a cache in place of the temps. That’s kind of what Team Badger does now…when the team has an outing we drop a permanent cache in the area to commemorate our having been there.
Well…events are events. There were created to mark social gatherings. Many events have come to include temporary caches placed for the day of the event. Events are events, they are not geocaches.
It would be an absolute nightmare for the approvers if temporary caches were allowed to have their own cache pages. Each cache would need to be reviewed to make sure if meets all the Geocaching.com guidelines. These rules would also hamper the creativity of the temp caches.
In the past we’ve left behind a cache to commemorate the event. I guess these could have been used to log the temp finds from the event. We’ve done away with leaving permanent caches for the events. When seeking permission for the event, we’ve promised the Park Manager that ALL caches would be removed after the event.
On a personal note, I will no longer be logging multiple “attended” logs for each temp cache I find at an event. I don’t know why GC.com eliminated the “found” logs for events, but perhaps it was to do away with this multiple logging. It seems kinda lame to me to have “attended” an event more then once. I’ll just be logging the events once. The time spent socializing with my fellow geocachers will be reward enough for me
[This message has been edited by GrouseTales (edited 04-07-2005).]
Grousetales has some good points … right now I’m wrestling with logging multiple finds on an event page … there’s a reason they changed those log types, even if we don’t agree with it. Personally, I don’t care about numbers any more … this is all about having fun with my family, and with new friends and the challenge of the hunt. I don’t have a problem with those that care about numbers, but it’s just not my reason for doing this. However, I still like being able to log each find at an event, mainly to briefly comment on each cache I found (because I think that good temp hides are worth commenting on) … yet it is a bit of hassel to log them all in (at least for someone like me that cares not about the numbers). I’m still not sure what I will do in the future. From the standpoint of someone planning an event, each temp hide is just as “important” (whatever that means) as a permant cache … I’ve actually put more effort into picking the spots for temp hides, as I want each one memorable and to have very exact coordinates (to avoid frustration with the quanity involved).
On another note … It’s fine to leave behind a “Memorial Cache” from an event (when property managers will allow it), but I still don’t like the idea of a permant cache having hundreds of event logs listed on it; as it looks odd going forward in the future, as others find the cache after the event is history. If I’m seeking a regular cache, I hope to find log entries/comments that deal with the cache I will be finding, not some long gone event.
quote:
Originally posted by EnergySaver:
On another note … It’s fine to leave behind a “Memorial Cache” from an event (when property managers will allow it), but I still don’t like the idea of a permant cache having hundreds of event logs listed on it; as it looks odd going forward in the future, as others find the cache after the event is history. If I’m seeking a regular cache, I hope to find log entries/comments that deal with the cache I will be finding, not some long gone event.I could not agree more!!
We often use the history to tell us about the area and the cache…having 100’s of logs that have nothing to do with the “memorial cache” would be confusing.
Another 2 cent.
We’ve been discussing this over in the Board of Directors forum as well. I’m glad to see the tide of the conversation in this topic starting to swing away from the idea of setting up a nearby cache to log multiple finds to represent the temp cache finds. Personally, I think we are taking the issue of “getting credit” for our hobby way too seriously. When we organized the first WGA campout, it was to be able to spend more time getting to know our fellow geocachers by spending time around the campfire. Now it seems like they have become cache-grab events with little time or effort to converse and get to know each other. Step back for a moment and think what our sport looks like to the outside world. If we are trying to gain respect for geocaching among land managers, the news media and “muggles” (and I think we are because of the comments I read in the forums that ask for more publicity, more cooperation with parks officials, etc.), then how do we expect them to take us seriously if we were to add superfluous rules about logging temp caches in alternative special permanent caches set up for that purpose? Let’s not take ourselves so seriously. Let’s stick to the “meat and potatoes” of geocaching. The outdoors. The search. The hike. The find. Let’s keep it a sport to be proud of.
I liked your comments, Ken!
I do like having a lot of temp caches at events too; but to me when I go to an event, I’m not going to worry if I find them all, I want to meet the people too. If I find them all great, if not I consider the found PEOPLE more important.So does this mean your going to have a July 4th event again? I hope! I’ve got more practice now, if you want to consider placing two caches, this time. But nothing so dangerous this time!
[This message has been edited by EnergySaver (edited 04-07-2005).]
You must be logged in to reply to this topic.