...
-Rusty-
-DeRock-
-Vanman-
-allenite-
-Tiki- (now reviewing Iowa)
...
title | Reviewers for Michigan |
---|
Note |
---|
|
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.
2. Vacation Cache/No Home Coordinates
...
...
...
...
...
...
...
...
...
...
...
...
9. Forbidden areas:
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Michigan State Designated Wilderness Areas - see link for wilderness maps
- Beaver Basin Wilderness map
- Big Island Lake Wilderness map
- Delirium Wilderness map
- Horseshoe Bay Wilderness map
- Huron Islands Wilderness map
- Isle Royale Wilderness map
- Mackinac Wilderness map
- Wilderness map
- Michigan Islands Wilderness map
- Nordhouse Dunes Wilderness map
- Rock River Canyon Wilderness map
- Round Island Wilderness map
- Seney Wilderness map
- Sturgeon River Gorge Wilderness map
- Sylvania Wilderness map
...
...
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.
Additional Logging Requirements:
"ALR's" are caches that require a finder to do more than just sign the log. Caches that require a picture to be posted, E-mail the answer to a question, or some other activity (in addition to signing the log) performed in order to claim credit for the find are considered ALR's.
As of April 4, 2009, Additional Logging Requirements can no longer be grounds for deleting a cache find. Geocaches can be logged online as Found once the physical log has been signed. If it is appropriate for your cache location or theme, you may still ask the cache seeker to accomplish an optional and simple task, however, cache owners may not delete the cache seeker's log if they choose not to attempt or accomplish the optional tasks. This guideline change applies immediately to all logs written from April 4, 2009 and going forward. Older caches with "additional logging requirements" (ALRs) are not grandfathered under the older guideline. If you own an existing cache with mandatory additional logging requirements, we request that you:
• Cease deleting logs based on additional logging requirements.
• Review your own cache listing to see if the ALR can be made into an optional and simple task, or whether it must be removed altogether.
• Adjust your geocache listing by editing the text and have a reviewer change the cache type, or archiving the listing and replacing it with a new Traditional or Multi-stage one in the same place.
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
...
...
...
...
...
...
...