To move or not to move

[+GPSJane]

So I have 2 caches. The one needs to be moved because we can't walk up to where it is any more. How far can I move it before it's not the same cache any more? At some point there's no point and I should just create a new one, right?

 

The other is a bit tricky because actually the place is still fine and the cache is there but it's inside a reserve that is very strictly controlled. I'd like to place a another cache outside the fenced-off part. It's a totally different cache with beautiful views of the city but it is too close. Also, I've had a log saying it's in need of an upgrade and actually there are better sites to put the cache. I could really redo the style of the cache including making it much larger.

 

Just for the sake of a second cache is not worth moving a cache but since it also needs an upgrade perhaps I should. What do you think?

Edited May 12, 2011 by GPSJane

[+Panther&Pine]

I'd say archive them both. It seems to me that both moves would make for a new finding experience and therefore should have new GC code.

[+Coldgears]

So I have 2 caches. The one needs to be moved because we can't walk up to where it is any more. How far can I move it before it's not the same cache any more? At some point there's no point and I should just create a new one, right?

 

The other is a bit tricky because actually the place is still fine and the cache is there but it's inside a reserve that is very strictly controlled. I'd like to place a another cache outside the fenced-off part. It's a totally different cache with beautiful views of the city but it is too close. Also, I've had a log saying it's in need of an upgrade and actually there are better sites to put the cache. I could really redo the style of the cache.

 

Just for the sake of a second cache is not worth moving a cache but since it also needs an upgrade perhaps I should. What do you think?

If you archive and remake the old visiters will come back... that's a plus.

[+StarBrand]

Sounds like a new caching experience in both cases - archive the old and create the new.

[+Bear and Ragged]

You can change the co-ords 600? feet, a reviewer can move it further...

 

If you walk a mile to the cache a 500 feet move of the cache is a small move, and very little change to the caching experience.

 

If you move a cache two feet to the other side of a long tall wall, you could say the caching experience has totally changed, despite the short move!

 

My opinion?

First one move.

Second one Archive it, and make a new cache.

 

But.

As Coldgears says: "If you archive and remake the old visitors will come back... that's a plus."

[+GPSJane]

Yeah you're right. Actually the second one has too many caches in the area to place all the new ones I was going to place. Now that I found the maps on Geocaching I can see this!

 

Perhaps I will redo one and move the other Thanks

Edited May 12, 2011 by GPSJane

[+SwineFlew]

I noticed that you got some older caches and maybe its best just to move it and not archived it. Thats my opinion.

[+Walts Hunting]

Actually it is 528 feet or .1 miles. If you ask a reviewer to move it further than that it goes through the whole review process again to make sure it isn't to close to another.

[Pup Patrol]

Knowledge Books:

 

6.8. Editing Your Cache Coordinates

Cache owners may find it necessary to move their cache and update their cache's coordinates. If the cache has moved less than 161m/528feet, the coordinates can be updated by the cache owner.

Be aware of other caches in the area. Your move may put your cache too close to other caches. Review our cache saturation guidelines.

 

6.10. Editing a Published Listing: Major Change.

 

If you need to change the coordinates beyond 0.1 miles (528 feet or 161 m), or change the type of cache, please contact your local reviewer. The reviewer will check the changes for adherence to the current guidelines and notify you when the changes have been made, or suggest that a new cache listing should be submitted. Please be sure to follow any instructions the reviewer may send you.

 

http://support.Groundspeak.com/index.php

[+StarBrand]

I noticed that you got some older caches and maybe its best just to move it and not archived it. Thats my opinion.

May I ask what the age of the cache has to do with anything??

[+two bison]

I noticed that you got some older caches and maybe its best just to move it and not archived it. Thats my opinion.

May I ask what the age of the cache has to do with anything??

 

As we age we get grumpier and more resistant to change.

[+AlohaBra and MaksMom]

So I have 2 caches. The one needs to be moved because we can't walk up to where it is any more. How far can I move it before it's not the same cache any more? At some point there's no point and I should just create a new one, right?

 

The other is a bit tricky because actually the place is still fine and the cache is there but it's inside a reserve that is very strictly controlled. I'd like to place a another cache outside the fenced-off part. It's a totally different cache with beautiful views of the city but it is too close. Also, I've had a log saying it's in need of an upgrade and actually there are better sites to put the cache. I could really redo the style of the cache.

 

Just for the sake of a second cache is not worth moving a cache but since it also needs an upgrade perhaps I should. What do you think?

If you archive and remake the old visiters will come back... that's a plus.

 

I am with this...another find! ...aloha..

[+lamoracke]

if these are your 2 South Africa caches which are from 2003, I might resist archiving and redoing especially since only 36 finds since 2003. Repeat business does not seem likely much with that. 2003 caches are not so sacred they should never be archived, but still, those are pretty old. I would resist archiving such old ones if your intent is to just make a new one close by. Your call.

[+Spraginator]

I'd say archive them both. It seems to me that both moves would make for a new finding experience and therefore should have new GC code.

 

I agree. If the finding experience is different, those who found the first two will want to find these also; and it's sometimes looked down upon to log a second "found it" log on the same GC#

[+Spraginator]

I'd say archive them both. It seems to me that both moves would make for a new finding experience and therefore should have new GC code.

 

I agree. If the finding experience is different, those who found the first two will want to find these also; and it's sometimes looked down upon to log a second "found it" log on the same GC#

 

Now that I see they are from 2003, I would say leave as is. Don't move or archive.

 

Old caches are fun, but not nearly as fun if you know they've been moved and esensially created into a new cache with the same GC#