Hey
Rob,
Since
you only get up there once a year, maybe you could ask for help from potential
seekers? For instance, you could put a paragraph in the cache description
asking for help from people who are planning on going to find this cache. Like,
if someone posts that the cache needs a new container or logbook, you could
supply that stuff to the next team to go up there. I did this in April for
a cache in Hawaii. The owner lives on the mainland, but they go to Hawaii
once a year in September. There was some maintenance required on their
cache, so I did it for them on my trip. It seemed to work out
well.
Given
the friendly and helpful disposition of the AZ Geocaching community, I'd bet
you'd get lots of volunteers.
-FroBro Q-Tip
Howdy,
Last January I placed a cache on Picacho Peak
(GCC5D6), this was to replace the lost and archived cache
Watch Your Step (GC0737). Its had been missing for over a year at the time.
Anyhow, the container that I had left was found by one team and then it
disappeared, though, I must admit that I have not been up to verify this. After
several teams logged nofinds, I changed it a virtual.
On May 23 a team found my virtual
and FOUND the old cache container, it was in good shape. They contacted
Team Marlinspike (the owners of the original cache) and got no response. I've
contacted Team Marlinspike as well and have received no response. Looking at
their profile page, they appear to be no-longer active in geocaching...it has
been over a year since their last find.
Here is the deal: I would like to take over
their container and change my cache from a virtual to a regular. I couldn't
think of any issues/problems with this procedure, so I thought I would check in
with the geocaching community for some feedback. Does anyone have a problem with
me adopting the container? I do realize that I need to go back up and
check in on things...though, this peak is a once a year thing for
me.
-Rob (Wily Javelina)
====
This message and any attachments are confidential. Unauthorized use
or disclosure of this message is strictly prohibited, and this message
must be destroyed immediately if received by an unauthorized recipient.
====