› Forums › Geocaching in Wisconsin › Help › approving coordinates for possible caches
- This topic has 11 replies, 7 voices, and was last updated 17 years, 7 months ago by
Team Deejay.
-
AuthorPosts
-
05/29/2008 at 3:11 am #1726604
Is there a way to submit only coordinates to reviewers to see if there might be anything wrong with them? We don’t want to write up a whole cache page, etc., and find out upon submission that there are issues with the place being one where a cache isn’t allowed, especially if it needs to be in that spot for it to work.
05/29/2008 at 3:29 am #1889701You can just submit a “skeleton” cache with just the bare minimum of information. Ask the REVIEWER to check your cache first and to wait to activate the cache. That should work. If you decide NOT to use those coords for any reason make you have the “test” cache coords archived or someone else might not be able to place a cache at your test coords.
05/29/2008 at 6:13 am #1889702Actually, this is not very good advice. Create the cache page but DO NOT EVER RELEASE A CACHE PAGE WHICH IS NOT IN THE FIELD. Just send the reviewer the GC number and we will check it for you. If you release the cache, no matter what you put in a reviewer note, it is very likely to end up published. We process a lot of caches and don’t need people putting bogus listings into the review process. Besides that, it is generally a good idea to put out the cache and leave it for a week or so to make sure it won’t get immediately muggled. This is especially true of urban hides.
05/29/2008 at 12:37 pm #1889703@Team Deejay wrote:
Actually, this is not very good advice. Create the cache page but DO NOT EVER RELEASE A CACHE PAGE WHICH IS NOT IN THE FIELD.
I think that’s what Mathman said when he said “wait to activate.” Completing the cache page but unchecking the “this cache is active” box before you click submit means reviewers can see it if directed to it but it doesn’t show up in their inbox to approve, correct? At least this is the way we’ve done it on a few such occasions.
On the Left Side of the Road...05/29/2008 at 6:59 pm #1889704@gotta run wrote:
@Team Deejay wrote:
Actually, this is not very good advice. Create the cache page but DO NOT EVER RELEASE A CACHE PAGE WHICH IS NOT IN THE FIELD.
I think that’s what Mathman said when he said “wait to activate.” Completing the cache page but unchecking the “this cache is active” box before you click submit means reviewers can see it if directed to it but it doesn’t show up in their inbox to approve, correct? At least this is the way we’ve done it on a few such occasions.
Yes that is what I meant. Thank you. I realize that cache reviewers have more than enough work to do without having to do “pretend” caches. The best way is to be positive of where you want to place the cache in the first place.
06/02/2008 at 12:02 am #1889705I will say that approximately 95% of the proximity issues are caches too close to the listed coordinates of other caches. All you have to do is create the cache page and then list the nearest caches to see this problem, but we get 20 to 30 of these a week. Many but not all are from first time hiders. The other 5% (those too close to multicache waypoints, mystery finals, and unlisted caches still in development) are no problem for us to work with the owners. The worst case I have seen involved a cache placement in Sanders Park in Racine, which took 4 tries. The first three tries were too close to three different mystery cache finals. But even then, the owner eventually found his spot.
06/02/2008 at 3:00 am #1889706What do the reviewers use to calculate distance from point A to point B? Does google earth or google maps allow for this?
06/02/2008 at 2:59 pm #1889707@nohandsgps wrote:
What do the reviewers use to calculate distance from point A to point B? Does google earth or google maps allow for this?
Google Earth works well, but it’s not faultless. (Right Dave 😉 ). I use it before placing any cache, to get an idea of what is open, but it’s not perfect.
The first thing about GE you have to remember is that when a cache Icon pops up, it’s never in the right spot. So, first, find an area you want to place a cache, and put that WP into GE. The, click on all of the surrounding area caches, and copy their coords from the cache page, and paste them into the GE browser. Then take your measurements from there.
Also remember that there may be puzzle caches and stages of multi-caches nearby that you must also avoid. Solving those puzzles, and doing the multi’s are the best way, but in some case, you can contact the owner of those caches and see if they’ll provide their coords.
The best advice I’ve seen is what Team Deejay wrote. Write up your cache page, then click the link that lists all the other area caches. If you’re good there, you should be ok, except once again, for the puzzles and multi’s.
What would be fantastic is a database that you could type in coords and give you a yes or no result, using all the info from GC.com including puzzle actuals, and stages of multis’ . This would have to work like the Evince coord system though, where you only get one shot every 10 minutes. Otherwise you’d have people triangulating to find puzzles.
06/02/2008 at 4:12 pm #1889708Different reviewers have different ways they like to handle requests to determine if caches are adequately spaced from others. As I wrote in my blog, I prefer to have geocachers create a cache page and include a reviewer note that the cache is not yet placed. This is especially helpful to geocachers who want to create multis or mystery/puzzle caches and need to create waypoints or a puzzle that list the digits for the final, which can be a lot of work and requires a reasonable expectation that their new cache waypoints and final will pass muster. I always check for reviewer notes before publishing a cache, so this works out fine for me. However, I don’t review caches in Wisconsin, so if you’re placing one in Wisconsin, you’re better off following the wishes of your Wisconsin reviewers.
06/02/2008 at 6:10 pm #1889709First, what Ken says is correct. Creating an UNRELEASED cache page is a good way to do a check. Before you send it to the reviewers, just go to the cache page and list the caches nearest to yours. The system will give you the distances for each. Anything under 0.1 miles is likely to be a problem, unless it is a mystery cache.
Reviewers can also get this distance for hidden waypoints, so if you think there is a puzzle cache or multi close by, you can ask us to check for you.
If you are just want a program to calculate distance between points, projections, conversions between formats, and other useful stuff, try the free program FizzyCalc. I use it regularly when working through things, and highly recommend it. I believe this will also work on a PC emulator on a Mac, but I have not tested this.
06/03/2008 at 4:20 am #1889710What about virtuals? Didn’t I read somewhere that the 528-foot rule didn’t apply to being near those, as opposed to other caches or waypoints, when looking to place a new cache?
And if we need to contact a reviewer, do we go through their reviewer name or their geocaching name (we know who you are, Oh Great Ones!). Just click on the name to send a note?–This is for questions before writing up a cache and submitting it.
06/04/2008 at 2:57 am #1889711@sandlanders wrote:
What about virtuals? Didn’t I read somewhere that the 528-foot rule didn’t apply to being near those, as opposed to other caches or waypoints, when looking to place a new cache?
And if we need to contact a reviewer, do we go through their reviewer name or their geocaching name (we know who you are, Oh Great Ones!). Just click on the name to send a note?–This is for questions before writing up a cache and submitting it.
You are right, virtuals and virtual stages of multi/mystery caches do not count for the proximity requirement. Neither do earthcaches, webcams, events, parking coordinates, questions to answer, or reference points.
And you can email me any way you like (just don’t call me late for dinner).
-
AuthorPosts
- You must be logged in to reply to this topic.