Publish / Find / Retract – Interesting Scenario

[CodeJunkie]

Very interesting. A new puzzle cache in Oshosh (final in Dr. Who series) was published earlier this week and has now been retracted. It obviously had some proximity issues, so I’m curious to see how this one will play out.

It still shows in the “My Finds” PQ and on “Recent Finds”, but does not show up in my profile pages under “Geocaches Found”.

This will be interesting to see how it plays out.

[rtrezrsnhvn]

oh, need to check that out for us too… we are planning on hitting #100 this weekend and I don’t know how that will impact it. Is it any different than for one that’s archived?

I wondered when that one published about it having issues. Pretty bold to have 12 caches ready to go, when you’ve only found about 30 yourself. I don’t feel comfortable placing 1 without really scoping it out vs making up a puzzle and then posting TWELVE!

thanks for the heads up!

[rtrezrsnhvn]

ok I see it was only the final… curious about a total retraction… no trace of it ….hmmm

[CodeJunkie]

The individual caches are OK, it’s only the final that got retracted. The challenge for the placers is going to be to recraft the final to match the values published in the field, or change all the caches in the field also to match a new final. I’d opt for only fixing the final and find a way to make it work.

In this case, I’m guessing there were some shenanigans going on. If they listed the final coordinates accurately it would never have gotten approved. My only guess is that they published a “bogus” final just to get it approved.

The statement about a new cacher placing is very true. It’s much tougher in an area like Appleton where there are many puzzles that you have to get a handle on. My first caches were in areas that I knew were outside the 2 mile radius for any puzzle, but I’m in a way more open area. Even today I’ve asked other cachers about general areas before thinking of a placement just to confirm I’m not going to bump into someone.

[rtrezrsnhvn]

@CodeJunkie wrote:

The individual caches are OK, it’s only the final that got retracted. The challenge for the placers is going to be to recraft the final to match the values published in the field, or change all the caches in the field also to match a new final. I’d opt for only fixing the final and find a way to make it work.

In this case, I’m guessing there were some shenanigans going on. If they listed the final coordinates accurately it would never have gotten approved. My only guess is that they published a “bogus” final just to get it approved.

The statement about a new cacher placing is very true. It’s much tougher in an area like Appleton where there are many puzzles that you have to get a handle on. My first caches were in areas that I knew were outside the 2 mile radius for any puzzle, but I’m in a way more open area. Even today I’ve asked other cachers about general areas before thinking of a placement just to confirm I’m not going to bump into someone.

interesting theory.. I suppose there are no repercussions for turning in the bogus numbers….

[CodeJunkie]

@rtrezrsnhvn wrote:

interesting theory.. I suppose there are no repercussions for turning in the bogus numbers….

1st – It’s against the rules (I’m assuming) because you’re supposed to submit accurate coordinates.

2nd – It’s hard enough placing a cache and knowing accurate final coordinates. Can you imagine trying to work around something the reviewers say is blocking you and you’re 99% certain there’s nothing there?

3rd – The reviewers can’t actually verify the coordinates by going to locate the cache, so they take us on our word that (see #1) the coordinates are accurate.

In all fairness, I know that some caches have had coordinates published that are “slightly off” to make the the 528′ work or have gotten a “waiver” because of crossing a large natural boundary like a river. In this case it’s within 150′ of a know physical container and 250′ of another known container, both of which are parts of non-traditional cache(s).

[glorkar]

Wish I would have know this was down earlier tonight! I all but one of the parts yesterday and went in to find the final tonight (without checking the cache page.) I looked all over for a good 20 minutes before giving up. Definitely have to see how this turns out.

[BakRdz]

The new final in the correct area just “re”published. All the previous finds are still there…including my FTF. 😉

[CodeJunkie]

@BakRdz wrote:

The new final in the correct area just “re”published. All the previous finds are still there…including my FTF. 😉

Interesting that I was emailed the final coordinates by having a notification bookmark set. I also checked at the prior location today and the cache was gone. Glad to see this one got straightened out.

[Author]

Posts