Complete_Control Posted October 10, 2008 Share Posted October 10, 2008 The problem is that this cache is placed within 120ft of another existing cache, GC1APZ3 [that is waiting to go live]. But i can't find this cache on geocaching.com or on the google map. I've never heard of this cahce and i can't figure out how to view 'GC1APZ3' either. My cache got rejected for a cache that doesn't exist? I'm confused.. Help! Quote Link to comment
+MissAmerica1 Posted October 10, 2008 Share Posted October 10, 2008 Someone may have one in the queue and it hasnt been released yet Quote Link to comment
+Polar B's Posted October 10, 2008 Share Posted October 10, 2008 (edited) Your cache got rejected for a cache that was submitted before yours but is not yet published. Probably the only thing you can do now is relocate your cache and resubmit Edited October 10, 2008 by Polar B's Quote Link to comment
+The Blorenges Posted October 10, 2008 Share Posted October 10, 2008 All physical stages of a geocache must be a minimum of 528 feet away from any other physical stage of any other geocache. In your case I would guess that another geocacher has already got a cache planned for that spot. Your local Reviewer is aware of this. There may be a number of reasons why that cache hasn't actually 'gone live' as yet, but it has priority. MrsB Quote Link to comment
Complete_Control Posted October 10, 2008 Author Share Posted October 10, 2008 The swine! Mine is great! Quote Link to comment
+OReviewer Posted October 10, 2008 Share Posted October 10, 2008 The problem is that this cache is placed within 120ft of another existing cache, GC1APZ3 [that is waiting to go live].But i can't find this cache on geocaching.com or on the google map. I've never heard of this cahce and i can't figure out how to view 'GC1APZ3' either. My cache got rejected for a cache that doesn't exist? The reviewer gave you a great explanation. The cache is not published, it is waiting to go live. Maybe it was sent back for a minor change, maybe it is on hold for a specific release date, etc. I would ask the reviewer to check on GC1APZ3 though... The GC# seems like it is from pretty early this year. It might have been overlooked for whatever reason. Quote Link to comment
+Prime Suspect Posted October 10, 2008 Share Posted October 10, 2008 I would ask the reviewer to check on GC1APZ3 though... The GC# seems like it is from pretty early this year. It might have been overlooked for whatever reason. Yup, GC1APZ4 (the following sequential cache) was published back in March. Six months is more than enough time to get a cache ready. OP should ask their local reviewer to poke the other owner with a sharp stick. If they don't respond DPQ, the OP should ask to be given the space. If they can't get their act together in 6 months, they never will. Quote Link to comment
+Brassine Family Posted October 11, 2008 Share Posted October 11, 2008 Hey there prime Suspect. I like your signature line... Ok, back to the thread. Quote Link to comment
+hukilaulau Posted October 11, 2008 Share Posted October 11, 2008 The swine! Mine is great! I've had that happen at least twice where mine was CLEARLY better than the one being planned! It's annoying but not much you can do about it. It does seem like there are certain areas where folks are "reserving" potential hiding spots. Seems like there should be some kind of time limit. In my area the reviewer will usually at least tell me the cacher whose cache is blocking mine so I can perhaps work something out... Quote Link to comment
Complete_Control Posted October 12, 2008 Author Share Posted October 12, 2008 Cheers for messaging back guys. I'll message the reviewer back and see if someone can poke the pending cache's owner. Quote Link to comment
Neos2 Posted October 13, 2008 Share Posted October 13, 2008 The problem is that this cache is placed within 120ft of another existing cache, GC1APZ3 [that is waiting to go live].But i can't find this cache on geocaching.com or on the google map. I've never heard of this cahce and i can't figure out how to view 'GC1APZ3' either. My cache got rejected for a cache that doesn't exist? The reviewer gave you a great explanation. The cache is not published, it is waiting to go live. Maybe it was sent back for a minor change, maybe it is on hold for a specific release date, etc. I would ask the reviewer to check on GC1APZ3 though... The GC# seems like it is from pretty early this year. It might have been overlooked for whatever reason. Even though the number is older, the cache waiting to go live may have only been recently created and submitted for review. Sometimes a cache won't work out for one reason or another and it never gets submitted. The ID is still good and can be recycled for another cache. Quote Link to comment
+niraD Posted October 14, 2008 Share Posted October 14, 2008 I would ask the reviewer to check on GC1APZ3 though... The GC# seems like it is from pretty early this year. It might have been overlooked for whatever reason. Even though the number is older, the cache waiting to go live may have only been recently created and submitted for review. Sometimes a cache won't work out for one reason or another and it never gets submitted. The ID is still good and can be recycled for another cache.Also, some people work on caches for quite a while before submitting them, so it may not even be a recycled ID number. Puzzle caches can fit this pattern very easily. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.