Questions on Moving a Cache

[+Lostboy1966 52]

I have a cache that I placed in a preserve a few months ago. I'm now planning some more hides in the area that will be themed to match this one.

The problem is, my new hides are on the opposite side of the park, well over a tenth-mile away.

My question is, can I relocate a cache a long distance and still keep the GC number (and logs), or do I have to Archive it and Re-Submit it as a new hide?

I'm not sure what option I would prefer yet; I'm just asking here because I'm too lazy to look up the rules.

[+TriciaG 573]

You can move it up to 528 feet / 161 meters. Anything beyond that can still (possibly) be moved, but requires reviewer assistance.

 

Needless to say, your new placement, either way, needs to still comply with saturation guidelines with respect to other caches.

[+CAVinoGal 656]

28 minutes ago, Lostboy1966 said:

My question is, can I relocate a cache a long distance and still keep the GC number (and logs), or do I have to Archive it and Re-Submit it as a new hide?

In my opinion, it would depend on the nature of the new location.  Will the hide be very similar to the original, or will it need a new description, hint, container, etc?  In other words, does the location make it a "new cache" experience?

 

Why move it?  Perhaps put new caches across the park, and also add to the series with more caches on the same side as the original?  Granted, I don't know the park or situation - how far are you  talking about?   How big is the park?

[+niraD 3288]

21 minutes ago, CAVinoGal said:

Why move it?  Perhaps put new caches across the park, and also add to the series with more caches on the same side as the original?

Absolutely. There's nothing that says that caches in a series have to be 528ft/161m apart from each other. One of my favorite series of caches is linked by a theme, but the caches are located in various places in 2 counties.

[+dprovan 1557]

If you move it that far, it's a different cache and should have a new ID and a fresh log.

[+sernikk 138]

10 hours ago, TriciaG said:

You can move it up to 528 feet / 161 meters. Anything beyond that can still (possibly) be moved, but requires reviewer assistance.

 

That's true, but there is a workaround. You can just move the cache 'n' times on the max. distance of 161 meters.

But I agree with CAVinoGal, why should you move this cache? Better leave it where it is, or just archive it if you don't want to maintain it anymore in this location.

[+IceColdUK 1040]

2 hours ago, sernikk said:

 

That's true, but there is a workaround. You can just move the cache 'n' times on the max. distance of 161 meters.

 

I believe that this would be flagged to the reviewers.  A good way to get on the 'naughty list'.  ;-)

[+sernikk 138]

3 minutes ago, IceColdUK said:

I believe that this would be flagged to the reviewers. 

 

That's true. Every coordinates change has to be confirmed later on by the local reviewer, but when the change is justified and subtle you should be fine with that

[+TriciaG 573]

27 minutes ago, sernikk said:

 

That's true. Every coordinates change has to be confirmed later on by the local reviewer, but when the change is justified and subtle you should be fine with that

Or just do it the approved way.

[+dprovan 1557]

2 hours ago, IceColdUK said:

I believe that this would be flagged to the reviewers.  A good way to get on the 'naughty list'.  ;-)

I'm not as sure it would be noticed, but to me, that just makes it like advising someone to shoplift: you get what you want and no one will notice, so that makes it OK. There's no good reason to try to fool the reviewer. If you want to move it further than is allowed by CO adjustment, the reviewer will move it for you. But I still say think hard about whether this is really the same cache or a new cache.

[+TeamRabbitRun 525]

4 hours ago, sernikk said:

 

That's true, but there is a workaround. You can just move the cache 'n' times on the max. distance of 161 meters.

 

You're missing the point.

 

What you're suggesting is to do a multi-move sneakily so that it doesn't come to the attention of a reviewer.

In other words, 'game' the system so that while you're adhering to the text of the guidelines, you're violating the spirit of the guidelines.

 

Tsk, tsk. Better to do it the right way, isn't it?

Edited Wednesday at 06:21 PM by TeamRabbitRun

[Unit473L 114]

1 hour ago, TeamRabbitRun said:

while you're adhering to the text of the guidelines, you're violating the spirit of the guidelines.

 

Isn't that the American way? 

 

I'll go back in my box now, let's keep politics out of GeoCaching!

[+TeamRabbitRun 525]

6 minutes ago, Unit473L said:

 

Isn't that the American way? 

 

I'll go back in my box now, let's keep politics out of GeoCaching!

 

Hey, Back in your box, you!

 

 

But, point taken.

[+cerberus1 3313]

19 hours ago, Lostboy1966 said:

I'm just asking here because I'm too lazy to look up the rules.

 

Kinda surprised you got the responses you did.  

[+dprovan 1557]

4 hours ago, Unit473L said:

Isn't that the American way?

Only when the guidelines aren't actually appropriate for the situation where they're being applied. In this case, the CO's perfectly within his rights to move his cache to a new location, so there's no reason not to do it through the reviewer. People could use this to sneak a cache too close to another cache, but that's not the American way; that's just cheating.

[+sernikk 138]

16 hours ago, TeamRabbitRun said:

In other words, 'game' the system so that while you're adhering to the text of the guidelines, you're violating the spirit of the guidelines.

 

To be honest I'm just saying it is possible to move it and if it's not a huge change it won't be anything bad. I don't recommend doing so, I'm showing only how it's working in reality. Like a fun fact in a way I see your point though and agree that we should try to do what was intended in the first place.

 

 

[+hzoi 1577]

On 1/13/2021 at 6:32 AM, sernikk said:

On 1/12/2021 at 8:29 PM, TriciaG said:

You can move it up to 528 feet / 161 meters. Anything beyond that can still (possibly) be moved, but requires reviewer assistance.

 

That's true, but there is a workaround. You can just move the cache 'n' times on the max. distance of 161 meters.

 

Yes - and if you do that, a reviewer will likely be in touch soon to archive the cache for circumventing the rule about moving a cache 528' / 161m, because they can see it. So, while it could be accomplished, I would not personally recommend it.

Edited Thursday at 05:11 PM by hzoi

[+Lostboy1966 52]

Ha! I'm not looking to do anything shady! Still laying out new hides in the park - nothing is official yet. If I move the one I'm thinking of, I'll resubmit it. Traffic is slow enough around here that I'm sure the few that have logged would be happy with an additional Found It chance!

[+fbingha 100]

If you want to move it move than .1 miles, just ask a reviewer to do it. You don't need to pass any moral test as to whether or not your cache is the "same experience". If it's part of a theme and it makes more sense to keep the same cache instead of creating a new one, let the reviewer know that and they will likely help you out. This has been my experience with themed caches that have become compromised and I needed to move them elsewhere in the same area but more than a tenth of a mile.