Temporarily Unavailable

[+Team GPSaxophone]

After clearing out the SE corner of town yesterday (minus a couple of DNF's), I did a search of nearby caches. As usual, I filtered finds so I could see what there was to hunt close to home. I was shocked to find 11 of the closest 20 caches were listed as Temporarily Unavailable! 8 of those 11 are disabled due to trail closures (high fire danger). Once went missing last month, one went missing in May, and one more has never been found (and the owner has never gone to look for it).

 

Do you have anything like this in your area?

[SunshineSnuz]

I've noticed that phenomenon in the past but right now only 2 in my first 20 are disabled (one has been that way since March 20th).

 

**edited b/c I can't count!

Edited July 8, 2004 by SunshineSnuz

[+Robespierre]

We had so much high water about a month ago that we had some of that.

[+welch]

We had so much high water about a month ago that we had some of that.

Same.

Flooding had disabled (and now archived some) caches, about a month ago. And now new flood warnings are being issued in some of the same areas

[+BlueDeuce]

Just last month Eastern Iowa had over 50 confirmed flooded caches. I really was amazed at how many survived even when hit by fast moving water. Unfortunately many have still not been replaced. Apparently FEMA won't cover lost ammo cans.

[+rusty_tlc]

I'm happy to report that there were only 4 in the first 10 pages. I did an unfiltered search just to make sure that none of my finds were AWOL.

One of the MIA's was a Traveling Cache that was actually in CA when it went missing.

[+strikeforce1]

I was shocked to find 11 of the closest 20 caches were listed as Temporarily Unavailable! 8 of those 11 are disabled due to trail closures (high fire danger). Once went missing last month, one went missing in May, and one more has never been found (and the owner has never gone to look for it).Do you have anything like this in your area?

 

I just did an unfiltered search. I found 7 in the first 5 pages.

 

1) pg-1 had 1 -- 5.9 mi out.

2) pg-2 had 3 -- 7.8 mi.out.

3) pg-3 had 1 -- 9.7 mi.out.

4) pg-4 had 0 -- 13.7 mi.out.

5) pg-5 had 2 --15.1 mi.out.

 

I guess we are doing pretty good here in Western NY.

[+tirediron]

Of the first aproximately 100 caches listed (out to about 14 miles) only eight were temporarily disabled/archived. I expect that the number will skyrocket though if we don't get some rain and the woods are closed...

[+flask]

i have 2 temporarily disabled caches that have been disabled for moths. it has something to do with weather conditions, but if i told you what exactly was the matter i'd have to have you killed.

 

uh, MONTHS. they've been disabled for months. one won't be so good for moths, either.

Edited July 9, 2004 by flask

[+Ambrosia]

We have only 4 in the first 10 pages, too!

[+quills]

we've been having a rash of that here. I've had 2 of mine go missing. and a few other cachers have some unavailable.

[+Runaround]

We don't have a real bad problem anymore. Keystone does a pretty good job keeping the local caches cleared up.

[+marmetion]

I have hidden 3 caches, 2 have been muggled , the other was on the wrong side of TPTB mountain . I have just about finished the 2nd leg of the last multiple I have hidden, (the previous 2nd leg disapeared, guess the geocaching stickers and the fact the item was non-working didn't mean anything to the one that needed it more than me) Depending on how long this one stays, will determine if I hide anymore, or just do the searching.

[+Team DEMP]

In the 1st 10 pages (covering a 13.7 mile radius) for my zip code search, there are 2 temporarily unavailable caches. That's only 1% of the caches so I don't think it's a problem in my area.