Sagefox

My first thought was to start deleting but then... We have a trackable that went missing in 2015 and two years later it gets a load of Discover logs in Europe. Tons of Discover logs. Turns out that it actually was there. I wrote to some of the discoverers and they said they actually saw it and one even sent a photo. It is still stuck in Europe and I'm trying to get it back to the US to complete its goal but it appears to be the real TB.

I've been led here to report this quirk which I want to do in case HQ coders want to look into it. Situation: During my "29 cache finds on the 29th" run I came to one specific cache, the next one on my route, and each time I clicked on that green treasure chest I would get the usual options page, i.e., the cache name and some street names. In other words, the map wants to know which nearby feature I want to click on. Choosing the cache name and hitting enter shuts off the gpsr. Each time, every time and with two different gpsr units. This does not happen if I click either of the two suggested street names. This was the only cache out of the 29 that this happened for and it still happens today. If I do a search-by-name for this cache it will get me into the cache page but when choosing some cache page options, like viewing logs, the units both shut off. Viewing the cache page description does not seem to shut off the units. I don't know if this is something to do with gc.com or with the Garmin maps. Cache: https://www.geocaching.com/geocache/GC37PHB_view-of-the-mountain Garmin 64s and Garmin 62s Maps: 64s: Garmin City Navigator North America NT 2017.30 62s: Garmin City Navigator North America NT 2018.2

Well... it literally meant the last 50 logs and it can't go back any farther. The only way it can do the hundreds of visits is when there are less than 50 logs subsequent to the visits. I guess I have to keep a closer watch on these "silent" visit logs.

I'm only deleting visit logs and I do that periodically which is usually after the trackable has moved on to a new handler. I haven't had a bogus discover log in years but with that Facebook page I imagine some of mine will get on the lists.

This will be helpful. The last tb I cleaned up had 360 visit logs and that took over an hour.

Is there a way to bulk delete "took-it-to" logs on our owned trackable pages? Over 600 visit logs by one cacher in one month is way over the top. I request that people not visit our trackables and for the most part people don't do that but some don't read the page or don't care what it says. I tried using the search feature for this question but didn't get anywhere with that.

Done! Thanks for the heads up.

Exactly!

Hat Rock additional note: Looking at the map again, the route to cache 35 is incorrect. It needs to take the perimeter road, I'll call it, around to the boat launch rather than the road to the housing subdivision out on the river as it now shows.

O.K., I'll start things off: Hat Rock State Park caches: This is a great addition to the CM route! We've camped at the RV park here a few times. It's a very nice stay-over when on trips to distant places. 35, 36, 37 and 38: Parking for all of these caches is near 35 in the boat launch parking lot then take the foot path near the boat ramp to 35. The path to 36 and 37 also starts at the boat launch and goes up to the old railroad bed. These two caches and have great views of the river. For 38, walk the bridge across the inlet to hike up to the cache for a great view of Hat Rock. We recall that the bridge is not driveable. 34 is above the old railroad bed which is closed to vehicles hence the T rating. The walk was o.k. and it's historical. This is the old river line that was abandoned in the 50s when McNary Dam flooded it a couple of miles upstream. Good view from up here too. 39: I would suggest removing from the route. The CM routing map thinks the service road is driveable but I'm sure it's not so it would make a long walk. Also there are two credible sounding dnfs which the COs have not responded to since last summer. 40 and 41: Map program shows driving the old railroad bed but that is closed to traffic. It is now called the Lewis and Clark Commemorative Trail. Access to these caches is from Highway 730. 40 is the historical site of old railroad warehouses and apparently a river shipping terminal. Edited 4:08pm with edits underlined.

We were able to check out these two even though the archived cache was not in play. The Squaxin cache is back on the table. We replaced the container and this is a great cache site. There is only one place it could be hidden and it was empty. Some snacky type trash tells me that someone stumbled on the cache during their woodland picnic. I removed the Thanks Guys container and will contact fellow Olympia area cacher Austin to get it back to him.

The Cloquallum Truck Trail is definitely off limits so that cutover will not be possible. Will post a photo of the sign when we get back home. The route could continue on the Cloquallum Road until it meets 108. We drove back to Shelton that way.

I met with a local cacher yesterday who suggested this route might well be closed or a gate could be open at one end and closed at the other... and that the first gate could get closed after people enter. He said he would not drive that road and he drives a lot of those back roads. He did give me the names of the two lumber companies that control the gates. Suzanne and I will take a drive out there late this morning to check it out.

Maybe I don't understand the problem or maybe it's fixed but I just click on the link above and it opens just like they always have.

It is posted on the route list. 6:00pm, McGlinn's Public House, 111 Orondo Ave, Wenatchee.

Thank you Mr. L for all that you put into this event. I fully expect that, as is typical, you will have arranged breaks in the weather to make this a comfortable day for us. I hope you've done the same for you back there where it looks like you might wish you had packed your skis and snowshoes. I hear that Washington and Boston are in for it but it will be milder around New York.

Seems people used to do that on the General Topics pages but I haven't seen that in a long while. I'm just asking if others are having trouble or if there are known issues with gc.com response times so I can eliminate possible causes. The site has been running very slowly for me for over a month. It is at its worst right now. Comcast has been to the house, installed a new modem and checked it out. The speed is more than adequate. This happens on three devices all less that three years old. A PC with a fast processor, a lap top with moderate speed and a Samsung Galaxy tab S4 tablet. The request for pages (to post logs, look at profiles, cache pages, etc) hang up with "waiting for geocaching.com" notes. I'm thinking that it is not the site because if everyone's computers were processing gc.com pages as slowly as mine there would be mass complaining happening. I just need to be sure.

That is just part of this game. Some folks are not very imaginative when hiding caches. I think you will find that there are quite a few hiders that do care about the quality of their caches. You might want to check out the number of favorite points caches have before you head out to "the hunt". You will have a better chance of not being disappointed if you search for high favorite count caches.

By myself in a suburban setting: 63 in 12 hours. That was some years ago and I know I could top that now. With a group of 3 in suburban and rural:101 in 12 hours. On a California desert power trail with one other person: 373 from 9 am to 4:30 pm. Rented an suv and we switched drivers every 25 caches.

Rats! We also will not be able to attend and I was soooo looking forward to it. Got our passports renewed, got enhanced DLs. We just got back from a 20-day Eclipse/Utah NP tour in 95 to 105 temps, limping van with water in the gas tank from a flaky gas station in either Maupin or Fossil, Oregon, and too many outside projects to do before the rains set in. We are even cancelling our Ice Age Floods Institute annual meeting and field trip in Sun Lake/Grand Coulee the week after Kewlona. Will be back on-line for Grays Harbor.

Yes, again, thanks for the numbers! I'm all numbered up and ready to go. We will raise our glasses to you Saturday night.

Oh goody! And it is an area we have not cached in. Looking forward to it.

Since the log says they didn't find it I would delete it and not be worried in the slightest about defending that action. The burden of proof here is on the finder. If they re-post a find and have a good story to tell then I would let it stand.

Yikes! How did we miss the TB Cafe during our eight nights in Santa Fe??? Usually I check for Virts when visiting new places. I must have been off our game.

Indeed - this thread is full of them. This is an awkward assumption unless we could somehow know that those 66 pages of examples are mostly or even partially full of unmaintained caches and that the F=DNF posters knew that and made their post because of it. No, I don't think there is any connection here.