Caching record

From GeoWiki
Revision as of 21:47, 13 October 2006 by Facitman (talk | contribs)
Jump to: navigation, search

Caching Records

PAGE IN DRAFT as at 13/10/06. Wait a day or so before flaming me please!

A few cachers have an interest in challenging themselves by trying for a caching record. The most obvious of these is to try and find the most caches in a single day.

Most finds in a single day

The record holders for the most caches found in a single day in Australia are:

  • Rabbitto found 33 on 20th November 2004
  • teamkittens found 43 on 1st January 2005
  • Rhinogeo and Facitman found 44 on 8th February 2005
  • Rabbitto found 56 on 12th March 2005
  • Acts2youthgroup found 77 on 7th October 2005
  • HawMorFords found 101 on 16th September 2006

Here's my (Facitman) suggested set of guidelines for consideration and agreement so as to try and setup a standard to be used by all record attempts.

NOTE: These are my rules. I used them when I found 58 in a day with Rhinogeo. I'm NOT saying that anyone finding a large number of caches in a day with other rules is wrong, a cheat or anything. They have not been written in response to any other cache-raid attempt ie. I'm not judging anyone, ok you hear me? Good :-)

  1. A record must occur on a single calendar day. Midnight to Midnight.
    ensures all logs are listed on the same date
  2. Only caches that have a physical container can be included in the attempt, ie. locationless, virtual and webcam caches are ineligible
    The purpose of a most in a day record is the logistics of moving and time required to find the cache, the above categories do not require this
  3. Everyone travelling in the group is part of the Cache-raid. ie. No designated driver, no numbers man. If a person is travelling with the Cache-raid they are part of the Cache-raid
    It's about a team completing the task not about how many people can help someone else do it
  4. The Cache-raid (ie All people involved in the attempt) must:
    • Visit every cache, ie. be present at the log signing
      no breaks, no rests otherwise a large team is more a relay than a team
    • Not have attempted nor found the cache previously
      What's the challenge if you've already found it, or have someone there to tell you where it is
    • No one can join the Cache-Raid part way through the attempt.
      again, its a team event not a relay
    • Participants can drop out but once out they cannot rejoin. (Be nice to let tired people go home without invalidating the Cache-Raid)
      Not fair to invalidate a whole attempt because someone has to stop
  5. If a cache has multiple waypoints each point must be visited as part of the attempt, no pre-finding of physical waypoints can occur by any members of the Cache-Raid
    It's about the most in a day, not over multiple days
  6. If a cache requires research prior to attendance at the physical waypoints and/or cache then some or all members of the Cache-raid can complete this activity. eg completing a puzzle presented on the cache page
    Pretty to force people to solve puzzles as a team
  7. Only one member of the Cache-Raid needs to locate the cache ie. not everyone in the group needs to independently find the box!
    It's about working as a team
  8. The Cache-Raid may not seek any support for finding the cache, ie no phone a friend calls for hints, locations or even DNF confirmations
    It's about the Cache-Raid team finding the caches
  9. A DNF is a DNF, no cache no find. The Cache-Raid may not place a replacement cache for a lost cache then claim a find.
    To fix a DNF and make it a find requires you to know and contact the owner, not all cachers have contact details of owners. Also, it's about what you can find on the day, DNF's are just part of caching
  10. The Cache-Raid must sign the logbook, a stamp or sticker can be used but the log must include a minimum of date, team name, find number for the day, time of the find
    You have to comply with the spirit of caching, log your finds. The date, time and number gives some detail which allows some level of transparency. Call it an audit log if you like