...
...
| title | Current Reviewers for Michigan |
|---|
...
-Rusty-
-Derock-
-Vanman-
-allenite-
-Tiki- (now reviewing Iowa)
| Note |
|---|
|
Michigan:
The biggest issues that prevent a cache from being published:
1. Proximity
Putting your cache too near an existing cache. This includes stages of other multi caches and solutions to other puzzle caches. Guidelines require 528ft (0.1mi) separation.
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
10. Restricted Areas:
(special permission or circumstance required)
- 150ft from Active Railroad
- Schools
- Airports
- Highway bridges
Other Issues/Suggestions:
Bad Ideas:
The following places have historically been bad ideas for cache hides.
While allowed by the guidelines, please think twice about the types of cachers that will be hunting your cache, and get adequate permission for your hides. In General, these are bad ideas:
- On Playgrounds - many cachers are single adult males and get parents rather upset if they are hanging around playgrounds looking suspicious.
- At Post Offices - postal areas are very sensitive due to problems with letter contents, and it's illegal to hide on on a postal box.
- At Banks - bank security does not hesitate to call law enforcement about suspicious activity.
Attributes:
Please take a minute when creating your cache page to add some attributes to your listing.
...
...
...
...
...
Challenge Caches:
A challenge cache requires that geocachers meet a geocaching-related qualification or series of tasks before finding the cache.
If you are thinking of creating a "challenge cache", please keep the following in mind:
1. It is generally considered "bad form" to log one's own physical cache.
2. Basing a challenge cache solely on some aspects of geocaching, such as 5 star terrain, may severely limit the number of cachers who can achieve the challenge.
3. Basing a challenge cache on non-accomplishments, such as DNFs, will likely prevent the cache page from being published.
4. Challenge caches may not require the publication of a new cache as a logging requirement.
5. Challenge caches may not require cachers to log caches that are disabled or archived.
6. An individual's attempt to complete a challenge should be independent of the actions of other cachers. A challenge is supposed to recognize the completion of an achievement, rather than the winner of a competition. (FTF's are an unverifiable competition)
7. Requiring cachers to find an explicit list of caches (rather than a broader category of caches) will likely prevent publication of the cache listing.
8. Using a challenge cache to promote one's own caches will likely prevent publication of the cache listing.
9. Challenge cache owners may also be asked to outline a long-term cache maintenance plan as caches involved in the challenge by be archived over time.
A challenge cache requires:
1. Geocaching-related
2. Affirmative (no DNF's or days without a find)
3. Reasonably attainable by the hider and a substantial number of other geocachers. This is two fold, 1. there must be local finders that are at least close to making it, and 2. there are enough local caches that make it at least almost possible
4. Logging requirements are logistically viable.
Handicap Accessible:
If you rate a cache with a Terrain Rating of 1 - this does not necessarily mean it is handicap accessible. Handicap Accessible means the location can be reached in a wheelchair, and that the hide be retrievable from a wheelchair (not on the ground or up high). If you rate your cache a Terrain 1 - please also set the handicap accessible attribute, to either Accessible or Not-Accessible
Cache disabled for an extended period.
The "Temporarily Disable" feature that allows you to disable a cache is meant to be used for no more than a few weeks. A disabled cache will continually show up in search lists, and while there's no cache to be found, it prevents someone from placing a new cache in the area that others can find. I realize that you may not be able to get to your cache right away, so I generally wait to post a note until the cache has been disabled for an extended period or the cache is brought to my attention. If there is no response to my note within a couple weeks, the cache will likely be archived. If there are extenuating circumstances, please post a note to your cache page. I look for notes posted in response to mine before archiving any cache, and sometimes other reviewers may be cleaning up cache listings and wouldn't see any personal e-mail to me.
Reply by e-mail
If you reply to the automatic e-mail sent out by the GC.com notification system in response to one of my notes, reviewers will not get your e-mail. Please e-mail your reviewer directly or via their profile.
Please include the GC# when e-mailing.
Reviewer Notes
We do not get automatic notification of Reviewer Notes placed on caches. Please e-mail if you've left a note you'd like us to see.
Geo-Trash
If you feel a geocache has been so neglected that it has become more litter than cache or if a cache appears to be totally missing and the owner is unresponsive to either an e-mail or posted notes on the cache page, you can bring this to our attention by either
1. E-mailing us the GC# of the cache or
2. Posting a "Needs Archived" type of note on the page. We do get auto notifications of the "Needs Archived" logs.
Adoption
If you would like to adopt a cache, you must make contact with the cache owner. Have them go to www.geocaching.com/adopt and set up the adoption to you. If the owner is gone (no longer active) and is non-responsive to your e-mail, geocaching.com no longer processes non-consensual adoptions, so it's your choice if you decide to help maintain it. Archived caches cannot be adopted.
Pre-Review
If you are planning a cache and wish to verify the location ahead of time, or possibly assemble the cache page in steps, please uncheck the "Yes, it's ready for review" box. If you'd like us to check out the listing before you place the cache, just e-mail us with the GC#. Creating the page ahead of time also has the added feature of "reserving the location" for a few weeks while you complete your cache. Normally, caches are expected to be in-place when they are submitted for review.
Publish at a specific date/time:
If you would like your listing to be published at a special date/time, please be sure to give us at least a full week's notice. We try to accommodate special requests but sometimes things just don't happen as we plan. We can't guarantee a specific time, but we're usually within a couple of hours.
Large series of caches
If you are planning on a large series of caches, please let us know ahead of time. This is so that we can both alert you to potential problems with completing your series and so we can pre-review at least some of them before a mass release date. We ask that caches be submitted far enough ahead of time that we have at least 1 day's notice for every 5 caches you submit.
Relocating a cache
If you relocate a cache, you can change the coordinates up to 528ft (0.1mi) via your cache page. If you need to move it further, please send one of us reviewers a note with the new coordinates and GC# and we can change it for you. Hopefully the new position doesn't encroach on another cache or it's stages, or we may not accept the new location.
Changing cache type
Generally, cache type changes (Traditional -> Multi, Puzzle -> Traditional, etc) are discouraged. Many users are very particular about their statistics, and changing the cache type can cause other issues as well. Often, we recommend archiving the old listing, and creating a new one in the same place with the new type. This has the added benefit of bringing cachers back to the area for the new hide. That said, there are valid reasons for changing a type. Contact one of us reviewers and we'll work through it with you.
Life outside caching
Please be kind. Since we are *highly compensated* by gc.com for our volunteer efforts, most reviewers need a *second* job to make ends meet. We make our best attempt to reply to your questions and cache submissions within 7 days. Many times we are quicker, however life often gets in the way of caching and reviewing, and we may sometimes take a little longer to get to you.
...
