msrubble

Possibly a corrupt PQ. If you have more than one PQ loaded on your Garmin, one could be interfering with the other. I spot-check to see whether caches from each PQ are showing up, after having some caches mysteriously not be vsible on my GPS. I am glad that you found this cache, so the problem is not as pressing.

I don't know that it's "great," but different from the usual. As a finder, not a hider, I've done one where the first stage held several sets of coordinates (four? six? eight?). The geocacher's job was to figure out which of them was the final location. Most were plausible possibilities. If the red herrings take a person to scenic/historic spots, cachers won't be too annoyed at guessing wrong and "wasting" time.

Cache rated easy, to try to convince myself:

Campgrounds. Took photos in September 2018. Requirements changed in May 2019. I thought it would be good to get some of my backlog posted and did not know or notice the new requirement of a minimum number of photographs. Luckily, I had another picture, although not a good one. It did get posted.

This is still happening, and it is very frustrating. I had a waymark declined because the category requirements had changed long after I took photos and marked coordinates. I wrote a note to reviewer, hit "save changes," and the site told me I hadn't changed anything. I uploaded a photo to meet the new requirements, and the site still told me I hadn't changed anything. And gave me the same message about making whatever changes the reviewer demanded. It took four or five tries. Finally, I put a space in the description, and I was allowed to resubmit. I still do not know whether the reviewer ever saw my note. So, that's two bugs, in my opinion. Adding a note to the category managers does not count as a change. As there is no other way to communicate with them about an issue, this is a problem. Uploading photos does not count as a change.

WGS 84. DDD MM.MMM (Degrees Decimal Minutes)

Took four attempts to get logged in. Went to the cache page of a recent find, searched for nearby caches, and was instantly logged out. And can't get in again.

In my (limited) experience, younger kids are not excited as much by finding something sneaky as by riffling through "treasure." On the other hand, once the local kids find out about the box of toys in the park, it's doomed. Besides counting, you could use colors. Or multiple choice. "If the bench is green, keep going straight ahead. If it is brown, turn left." You could put a simple jigsaw puzzle in the first or second stage. Put the puzzle together to see the coordinates. Or a photo of the final location. Treasure map? Maybe you could make it spy-themed. Talk about spy gadgets and tell them they are looking for something small that is a disguise, and what it can hold (the logbook).

https://www.geocaching.com/hide/createcache.aspx

From the last few caches I have put together: collectible uncirculated coin, so it won't get scratched scrapbooking-type sticker, so the backing won't peel wristband, so it won't get dirty marbles, to give away a set fridge magnet, to prevent tarnishing and/or inhibit sticking to other items The last is rationalizing, I know. So besides paper, I might consider plastic bags for metal or textile items. I also put dog or cat toys in bags because of the ick factor--I want the pet owner to know I didn't find it in the woods somewhere.

Yes, benchmarks are interesting. Not all of them are included in geocaching.com's database. If you can find them in another database, like NGS, or your state's geodetic database, you can document your finds in the U.S. Benchmarks category on Waymarking.com. I could not find either of these marks in the NGS listing for San Juan County, New Mexico. You can look up all the marks in a county here. You might find more help in the Benchmarking forum.

Minnesota state parks are open. County parks where I have hides are open. If a city has closed its parks, I hope they post it somewhere at the entrance to the park. Otherwise, how do they expect peple to know?

If it's the Facebook page that's been getting a lot of attention here and in the Geocoins forum recently, it is not the owners of the trackables who are posting the tracking numbers. It is some jerk who is running scripts to check every possible combination. If you know what set of characters some type of geocoin or trackable tag starts with, you can try a lot of possibilities to fill in the rest. If you get a hit on geocaching.com, voila, it's an existing trackable. The people who use those codes to log travel bugs they have never seen are trying to run up the score. For them, it is not the point to move something physical from one geocache to another. The idea for them seems to be to find as many codes as they can that work.

Last night I was able to solve some multis on my computer. I added corrected coordinates on the cache pages last night, and set a pocket query that includes those geocaches to run today. When I loaded the pocket query in my GPSr, the corrected coordinates were given for only two of the solved caches. The other two still had the original coordinates for stage one in the PQ, despite having corrected coordinates on the cache page. The affected caches are not in any other PQ, and were not downloaded individually. Because there is more than one PQ server, is there sometimes a delay in including corrected cooordinates?

Jayeffel, to load an individual cache to the eTrex, it should be as simple as connecting the eTrex to the computer, clicking "Download GPX," and saving to the GPX folder on your Garmin. In Windows, the Garmin should show up as if it were a drive, and the folder to save it to will look like D:\Garmin\GPX. As a Premium Member, you can also use Pocket Queries to get the details on multiple caches in one file (or two, if there are other associated waypoints). That is a zip file. You can download it somewhere, then extract the file(s) to the same GPX directory on your Garmin as you would put an individual GPX file.

Ice melt crystal. In an island cache.

This problem is caused by cookiebot.com, as noted in the Release Notes forum thread on the California privacy law.

Cannot see cache logs on mystery or regular caches (haven't tried others) in Seamonkey on Windows 10. I can see them in Chrome. but there is a noticeable delay in loading.

Have you asked the owner? If the owner really did ask the previous cacher to bring it home, I would recommend trying to leave it in a nearby cache. If you're being asked to travel hours out of your way, on short notice, that's another story.

That was not on the site when rustynails. asked. Nor was it on the company's main site.

A new bug for me: I cannot use the Advanced Search page https://www.geocaching.com/seek/nearest.aspx in Seamonkey on Windows 10. I am trying to map caches hidden by a particular owner, but when I click on the dropdown arrow to change the default By: By Postal Code, I am redirected to Geocaching 101, https://www.geocaching.com/guide/ Intermittent problem. This happened the first time and not the second.

Groundspeak fixed the inability to write a log in the "new logging experience," and, I think the inability to download a GPX file from a cache page. Blocking cookiebot.com allows me to see events logs at the bottom of a cache page without clicking on View Logbook, and restores the small map on cache pages.

I had to hit "refresh." Then the "agree" popup went away.

It is helpful to note browser or app and operating system, plus any add-ons, when trying to troubleshoot problems. This update has affected different set-ups in different ways. The first person is not using the web site to post logs; they are using a geocaching database program for Windows (not from geocaching.com). Seamonkey is a browser in the Firefox family. It's open source, and sort of like Netscape used to be. FF71-64 bit is a specific version of Firefox, 64-bit, on Windows 10. Noscript is an add-on that blocks Javascript. cookiebot.com seems to be the source of the new "This site uses cookies" panel, and as someone speculated above, is being promoted to web sites as a solution to privacy laws. You don't have to worry about any of this. Whether you are or aren't seeing problems, it will help the Groundspeak developers (and your fellow geocachers) if you say what browser or app and what operating system you use.

Same here, in Seamonkey on Windows 10. Try opting out of the "new logging experience."