The Happy Hodag!

I just spotted this thread, and I know it's been a few years. I've been to Saint Louis a few times, and always make it a point to go to Forest Park. There's something for everybody there. -The Happy Hodag!

Welcome back to Geocaching. Are you on Facebook at all? If you are, look for a group called Fox Valley Geocachers. If not, you could always look for event in the area. If you're willing to wait until December, you can attend GCA0WAW hosted by Walking Adventure. That is a very well attended annual event with folks from the area and other parts of the state as well. Another option is to seek out a cacher by the name of King54130, she is willing to help out cachers with any level of experience, and is a great ambassador of the game not only in the greater Appleton area, but for across the entire state of Wisconsin. Good luck in avenging your DNF's. -The Happy Hodag!

The journey is what it's about to me as well. There have been caches that I've visited but never found, or at least didn't find on my first visit. My attitude there is that I get another chance to visit that spot later. I can certainly understand the frustration with the Brass Caps and the YOSM, but I also understand what CathyH had to say as well. While I agree that these caches should have been archived because they were considered locationless caches, I think they should have been archived 12 years ago with those that were actually listed as locationless. As far as the original reason for this thread, the moving caches. I'm planning on traveling to Saint Louis and had my eye on the moving cache there in Forest Park. I'll still visit that park because there's so much to see there, it's just that there's one less cache there to be found. That one was listed as a multi with the first waypoint staying in one spot, but a waypoint after that being the one that moved. I can certainly understand why all moving caches had to come under a blanket action though. -The Happy Hodag!

I agree here. They could have at least given the CO's a couple days warning to decide how they would handle it. I had seen several of these on vlogger channels on YouTube, where someone would bring a moving cache to a mega event. This is where the TB option can come in handy. -The Happy Hodag!

And in case anyone was wondering, the GC code for the cache I've been watching is GC1D0F.

I have a list of targets for an upcoming trip to Saint Louis, and one of them was the moving cache in Forest Park. Just less than 20 minutes ago, I saw an e-mail from HQ stating that the cache had been archived (and also locked) and that the CO could convert the cache to a TB. Goodbye moving caches. -The Happy Hodag!

I never could figure out GSAK. It is the least user-friendly interface I've seen in a long time. Honestly, the only thing I use it for is logging caches. I could never figure out how to do much else even with help from others. Thankfully they have a notification if you're about to log a "Found It" a second time. I use GSAK for about 10 years now, I only use the gc website when working on mysteries (and links to checkers) and for the occasional check on caches we did when I want to know if others logged on the same day or if there are issues with trackables. With all the "improvements" on the gc website working offline with GSAK is a lot easier. It did take some time to get the hang of it but I would be lost without it. I guess I'm on the opposite end of the spectrum there. I've kept using the website for things like updating coords, creating routes, etc, and have a good handle on how to do things without GSAK. -The Happy Hodag!

I never could figure out GSAK. It is the least user-friendly interface I've seen in a long time. Honestly, the only thing I use it for is logging caches. I could never figure out how to do much else even with help from others. Thankfully they have a notification if you're about to log a "Found It" a second time. -The Happy Hodag!

This change in how the logging screen looks will take some getting used to. I think I'll be using GSAK more to log my caches. -The Happy Hodag!

It looks like the other changes are in place preventing you from logging a second find/attended on a cache/event. There are several megas I've seen where cachers will log months in advance that they attended already even though the event is still months down the road. One current example is the upcoming West Bend Cache Bash, someone will be disappointed to find out the hard way they won't be able to log the event the day of. -The Happy Hodag!

I have seen a couple examples of why some cache owners have logged such on their own caches, but they are unconvincing. For the life of me, I don't see the necessity. If I'm looking for my own cache and I can't find it, I either replace the cache on the spot if I have one (and then leave an "Owner Maintenance" log stating so), or if I don't have the means to replace the cache, I disable it (again, there's a log for that). Similarly, if one of my caches really needs maintenance, I am an adult who can remember things and can make a note of it somewhere, or if it's really that bad, I can disable the cache. Disabling a cache that needs maintenance or has gone missing also gives me incentive to get my butt back out there and fix or replace the cache before a reviewer gets involved, rather than just stringing people along with "Yeah, I'll get to it eventually" and trying to hide the cache's true state from the reviewer. If someone has a really convincing argument on why cache owners still need to be able to log DNFs and Needs Maintenance on their own caches, I'd be curious to see it. +1 !!!!!

I'm one of the few cachers in my area who actually pays attention to what people say in their logs, regardless of type. My way of handling maintenance would be to at least post a note in response to someone else even if they don't post an NM log of their own. That way, I can go to my logs in the last 30 days and see what caches of my own are there for future reference. When I end up performing the needed maintenence, I log an owner maintenance log to say I performed the necessary maintenance. There have also been times I've had to disable a cache as well. Upon enabling later, I put up an owner maintenance log as well. -The Happy Hodag!

Just a couple thoughts here. If you own a cache, why would you need to claim a smiley on it? You'll still be able to adopt a cache you've already found, and you'll be able to claim you attended an event you own. Do you need to let other cachers know there's an issue with a cache you own? Instead of throwing up a red wrench, just disable the cache. Check out the 2017 West Bend Cache Bash, someone has already logged with "Attended" even though the date of the log is last October. They'll be pretty upset that they can't log the proper attended log this coming August when the event happens. Double logs in general, I actually know a guy who claimed a second smiley on a cache but didn't realize it. . .this was on a day we were caching together, but we never went there. I made sure he deleted the duplicate log. As far as caches I own, I make sure to delete duplicates, and recently did this on an event I hosted. -The Happy Hodag!

There's a local puzzle cache here that had a homeless encampment right next to the final about 2 1/2 years go. If you want to check that story out, go here: https://www.geocaching.com/geocache/GC1A6EE_virtually-famous-1 I'm sure I found the way in because of the homeless couple. -The Happy Hodag!

Another idea for us Premium Members is to create a Pocket Query just for Event. That way, you can refer to the Pocket Query to search for Events in the area that you want. Another nice thing about this is that you can change the dates on the Pocket Query so you only need to see events that have yet to take place. -The Happy Hodag!

The recommendation of putting the TB's in one of your caches, even if just virtually, has me thinking. . .can a CO still mark TB's as missing if they're listed on a cache they own? If this is the case, the OP could have dropped the TB's in their cache, then marked them as missing. -The Happy Hodag!

I listen to Pod Cacher and the Geo Gear Heads. -The Happy Hodag!

Are you loading caches one at a time? I see you're a premium member, so I would suggest creating a pocket query for the area you're loading caches in. -The Happy Hodag!

I'm so glad I'm not the only one out there. Anyone else? -The Happy Hodag!

And yet it has 18 DNFs? Apparently there's an actual cache there in addition to the building. I found this one last October and simply signed the building. -The Happy Hodag1

I have an eTrex 20. It offers everything I need in a GPS for Geocaching and then some. -The Happy Hodag!

I was FTF on a film can in a guardrail. Pretty boring at first glance, until you popped it open to find the logbook was in a roll of film. -The Happy Hodag!

Another thing to consider is using a date range of events, this will eliminate events that have already taken place. -The Happy Hodag!

Another way is to use GSAK since you can sort caches by when you logged a DNF. -The Happy Hodag!

IMO, favorite points are meant to highlight active caches. What I do when I give a favorite point out is I also put that cache on a bookmark list. That way, I can reclaim those favorite points when a cache is archived. Even tho I have over 70 favorite points available, I still want to have some on reserve in case I come across a bunch of quality caches down the line. -The Happy Hodag!