Jump to content

OReviewer

+Reviewers
  • Posts

    289
  • Joined

  • Last visited

Posts posted by OReviewer

  1. Cache has been published, with my apologies. It was pointed out that the multi had a virtual start so the proximity issue was moot.

     

    Any insight or clarification is greatly appreciated before I plead my case to the reviewer (a bit scared - think they're starting to get ticked).

    Not ticked at all. You've given me timely respectful responses; that's all I can ask for on my side. I would rather publish than say no but I have to follow the guidelines.

     

     

    Are you using Groundspeak's free Geocaching app? If so, then it will show only traditional caches. Since your cache apparently conflicts with a multi-cache, the free app won't help you.[/Quote]

    Good question. I was wondering this myself. I suggested something was being filtered and that would make some sense.

     

     

    Idea number 2: ask the reviewer whether they can give you a nudge about which direction you could move to place a cache.

    Well, since it was the posted coordinates I gave her the name of the cache, the GCcode as well as the distance to the coordinates. Even when it is a hidden waypoint, I give the GCcode and name. This allows the cacher to know which is the problem and do the cache.

     

    Anything more would give them an unfair advantage; maybe allowing them to ignore the puzzle/earlier stages.

  2. If it were in one of the regions I review, it sounds like 4 events; 1 per day.

    Thanx! :)

    There is definitely flexibility in my mind on it, but it would have to really show that there is some intent that they aren't just for another smile.

     

    (Generic) You do a breakfast event right before a cito and they both reference each other, it isn't going to fly. (If you don't reference them, it probably won't fly either)

     

    If you're, (again, generic), running a breakfast in one area; and it doesn't appear to be placed for the CITO; there is a chance.

     

    It really is one of those "you know it when you see it" guidelines. The issues is the more you put into writing on distances and times requirements, the more people will try to make events fill those rules. By not having them, there is some flexibility based on the scenario.

     

    My template for this has some other good information (and much of the wording stolen from others):

    The intent of a geocaching event is to have geocachers gather, have fun, perhaps share some trackable items, perhaps have refreshments or a picnic, and of course to collect an "attended" smiley.

     

    Having the same group go from place to place to place, multiple events in a day, is not at all within the expectations of a geocaching event. Traveling a significant distance to a second or a third event on the same day might be OK if the events are in different towns and stand on their own merits as geocaching events. But somewhere after the first event there is a line, which when crossed, changes the experience from a geocaching event to an attended log collection exercise.

     

    We believe the social part of geocaching is very important and we encourage geocaching events. Attended log collection exercises are not at all within the scope of geocaching events.

  3. Granted, given the fairly subjective nature of the clarified guidelines, I realize that there is no catch all answer regarding event proximity. I'm just looking for a general idea, before I start typing up event pages. For instance, around the tail end of October, in the Ocala National Forest, there is a four day gathering known as Florida Finders Fest. There is a central site, where cabins are, and where tents can be set up.

     

    Typically, there will be a hot dog eat & greet on Thursday afternoon, at the central site

     

    Then, Friday morning kicks off with a couple events which occur at about the same time frame, a Jeep run and a kayak paddle. At a guess, I'd say there was about 10-20 miles between these two. Both are about 10 miles from the central site. Around 5:00pm Friday, there is a chili cook off at the central site. Around 9:00pm Friday there is a night gauntlet event / AFDB contest about 3 miles from the central site. These used to be two separate events, but they were combined into one due to the stacking guideline.

     

    On Saturday there is the main event, Florida Finders Fest, at the central site.

     

    On Sunday there is a CITO of the central site.

     

    If this occurred within your Reviewer area, what changes would need to be made?

    If it were in one of the regions I review, it sounds like 4 events; 1 per day.

  4. This is the archived listing: http://coord.info/GC2AEHW It's not obvious what happened from the listing, but the "Duke Farms Foundation" stated that the area was "closed" and the cache should be removed and then a few weeks later the geotrail came out with caches in the same area.

    The closest cache, is about 0.2 miles away on a different trail and none were put on the trail or in the area. I think that archival might have been legit, at least by the e-mail from the park.

  5. Oh yes, i know and wholeheartedly agree with OReviewer's idea.

     

    However, and i'm speculating of course, this probably wouldn't work since the point of the new caches is most likely to attract as many cachers as possible. Rangr Dave and others involved with their project realize that many, maybe even most, cachers don't want to spend the time needed on multis and puzzles just to get one smiley. For them, placing traditionals is the way to go since they are more popular.

    Actually, the multi set up this way is actually the most optimal for those numbers hunters as they aren't going out of their way (or not very much) since the starting location is a place they are already going for the traditional cache.

     

    FWIW and IMHO, a good informational training geotrail should have a combination of many cache types; but that's just me. Also, I agree with what many said earlier, I got to events for the people, not the caches placed. For the last 10 years, we've held a pot-luck, family type event at the same park. We've run between 50-100+ attended logs on each one of them with the average attended log being about 3 people. The hosts have never put out a cache for this and we still have consistently good attendance for this. There is always some turn over in the park (or very close by). No one in the area feels a need to carpet bomb the area with caches every year or churn the ones that are there. In 10 years of holding it, I've never heard a single complaint about cache numbers.

     

    That said, as a reviewer, I've seen many comments about "putting out these 6 parking lot caches or someone won't come to my McEvent".

  6. Rangr Dave posted a note for XMas Presents for Sue&Barry (Unknown Cache) at 11/26/2013The cache that is requested to be archived is within .1 mile of an area that has great historical significance to the park. What greater way to bring someone there and educate them than through a cache?
    Make it a multi...
    Unfortunately, we all know this is about numbers. Making it a multi or part of a mystery would not bring in the numbers like a stand alone traditional would.
    I believe the point O was making (correct me if I'm wrong) is that there is a creative and collaborative way to making these proximity issues work for all affected.

    That is correct; making it a virtual stage of a multi allows you to take someone to a location that already has a cache at it, show them when you want, explain what you want and does not disrupt the current cache.

  7. Rangr Dave posted a note for XMas Presents for Sue&Barry (Unknown Cache) at 11/26/2013

     

    The cache that is requested to be archived is within .1 mile of an area that has great historical significance to the park. What greater way to bring someone there and educate them than through a cache?

    Make it a multi...

  8. As one of the reviewers of this area, I was waiting for more information before I acted on the Needs Archive log. I see the cache owner archived the listings already, making the situation on my a little bit easier.

     

    From my standpoint: Land managers request trumps all. I would have archived the listings but would have required a direct e-mail with a parks/municipality return email address. Anyone can create a caching account and name it whatever, say they work for whomever.

     

    I would make this general suggestion to Ranger Lynn or any other official who plays the game AND wants to act the part of a park official. Create an official park account that is not a player account. Segregate the two accounts to remove the look of impropriety or anything like that. One official e-mail to the reviewers and we know forever that things from this account are park sanctioned.

     

    As for the general practice of "I have permission and want that spot from someone who doesn't", it sets a bad precedence and creates cacher to cacher disharmony. I don't know the logistics of this geotrail but in general, I feel you gain more by working with the community and/or individuals than bulldozing over them.

  9. Go into a business? Not against guidelines.

     

    I would say #2 says it is against the guidelines...

     

    Commercial geocaches are disallowed.

    1. It has overtones of advertising, marketing or promotion.

    2. It suggests or requires that the finder go inside a business, interact with employees and/or purchase a product or service.

    3. It contains links to businesses, agencies, commercial advertisers, charities, or political or social agendas.

    4. It contains the logo of a business or organization, including non-profit organizations.

    5. It contains the name of a business or commercial product.

  10. I even have a template* for it!

     

    A logbook needs to be signable by anyone without the need to use any electronic or special equipment. Please add a paper logbook or sheet that allows pen/pencil. Objects that utilize connectivity do not meet the guidelines as they represent a potential security risk.

     

    *In almost 10 years of caching, I'd never found a flash-drive log and then I found two in one day!

  11. What's your opinion on forgotten cache challenges? Do you still see them as publishable (if the number of caches to be found and the period for which they are unfound are appropriately chosen) or do you regard them as no go under the current guidelines?

    Its like anything else, it depends on how it is written. I believe that while a challenge cache should be challenging, it should be doable.

     

    The one or two that I've published, I believe, have been point valued forgotten caches. I'm making the number up but I would publish it:

     

    Forgotten Challenge: Must have 100 forgotten points.

     

    3 points for a cache unfound for 3 months

    6 points for a cache unfound for 6 months

    9 points for a cache unfound for 9 months

     

    and so on. The longer the cache is unfound, the more points it is worth.

     

    Again, this lets people work on the challenge at their pace, does reward people for finding unfound caches where as doesn't hurt people after the unfound cache is found. I've seen older ALR caches (pre-challenge), where they were near impossible for people do them because once the 2 year unfound cache was found, you'd have to wait over a year and hope the next one wasn't found before then.

     

    The other issue I have with strict forgotten caches challenges, instead of letting a missing forgotten cache die when they should, some would replace them quietly to be able to say they found it; even if there was a string of DNFs. This never sat well with me. Challenges should encourage you to play the geocaching game, not do sketchy things just to qualify.

  12. I agree it is not a static list.

     

    Not wanting to sidetrack too much about this specific cache, but the "fixed list" (or not) could have been the reason for the difference of opinion. The cache description does contain the specific list of 20. It also lists the next oldest alternatives and has clear rules about allowing caches from the "backup list" if one of the 20 is not available etc.

     

    So I'm just speculating.. but it is possible the reviewer considered this a fixed list, and appeals did not.

    As a reviewer, I see it as a fixed list. When I get challenges like that, my answer is something of combining what the cacher wanted and what the reviewer wanted. I would suggest "Find 12 of the oldest 20 caches". This is challenging, is not a fixed list and can be listed rather quickly.

     

    The reason it is a fixed list (to me), is that if one of the caches goes missing; anyone actively working on the challenge has to wait for it to get fixed (or archived) to complete the challenge. The leeway list (12/20) gives caches the ability to keep working even if a couple have problems.

×
×
  • Create New...