All Activity

I guess I don't quite see the problem since Garmin devices don't allow you to do anything while they are in mass storage mode, unlike other devices that still let you use them while you are tethered to a computer. Well, here's hoping that iCaching builds in a MTP protocol to allow it to directly communicate and write data to the device/SD card.

Meh... I've found TRADITIONAL caches that were in locations similar to that. They were placed on public pedestrian/multi-use paths that went through a freeway interchange, and the satellite images looked like yours, except that it was a TRADITIONAL cache icon, not a mystery/puzzle cache icon. There was no legal access to the cache locations from the freeway, and the listings warned seekers not to try to access the caches from the freeway. But it was a lot of fun figuring out how to access the cache location safely and legally, and where the nearest trailhead for the public path was. Many T5 caches are a much bigger risk for "potential tragedy" than these caches. I certainly hope cache owners don't stop putting out interesting caches because they're terrified of being "a CO that's responsible for the potential tragedy".

Arisoft, are you thinking about bonus caches? I thought we can only have a single bonus cache coming from any one (or many) other cache. Many to one, one to one, but never one to many or many to many. Or are you thinking of something other than bonus caches, more like an alternative way to find coordinates for many other puzzle caches...

This, I believe, is still publishable. “5 of 7 oldest caches in county” is similar and many of those have been published recently.

If legible, and anywhere close to what you describe, I agree. We've never found proxies like your awesome examples. What we often find are illegible, crumbled, piece of paper with a soaked science project in-between two pieces of laminate. It's junk, just like most other damp paper pulp in the bottom of a cache, and I pitch it with all the other carp (gum wrappers, twigs, sand...),

Gca9b80

Do you have an example where such a thing was allowed in the last 7 years?

I'm not totally unsympathetic but I don't completely agree either. You say: Doing their best? They can figure out how to post on Reddit but they can't figure out how to read the "Quick guide" in the app which explains that, "Most often, the final container is not at the posted coordinates"? Or maybe go to the Geocaching.com and find an explanation for what all those different icons mean? At one time, in the app, when you clicked on a cache type for the first time a message would pop up explaining about the type. To move on you had to click "OK". As an experienced user it was really annoying but for a new user it could be helpful assuming they bother to read it. It would only pop up once (but would sometimes reset after an app update). I haven't seen it in a while so I don't know if it still happens for new users but, to some extent, it would address the issue you bring up.

If it is not a list, but is a database search, and the cache owner has no way to select the caches, it should be allowed. For example, most favorited caches and oldest caches etc. are typical allowed challenges.

Planning a road trip and tried to print out the list of caches that I've chosen using finds along a route. I have three of them, and when I try to print, each one shows a PQ list that has been deleted for some time. The new ones do not show up. Cookie setting is for "all". Any idea why this is happening? Thanks.

Do you think maybe this applies?

In this case, the time it takes an engineer to fix this is less than the time European geocachers waste turning dots into dots millions of times.

Wrong, in Finland CSV separator is a semicolon. And it does not matter if the data in a file is binary, hexadecimal or ASCII, because the problem is in the user interface which tries to understand many formats automatically.

Speaking as an American, I would agree that most people here (who haven't traveled) don't know, and would be surprised to learn, that a comma is used as a decimal separator in many parts of the world. However, at least from my experience travelling, people living in Europe and other areas that use a comma do understand that both are used. When I first travelled in Europe in 1973 I remember being surprised to see commas as a decimal but after a few moments of contusion I had no trouble adapting to the local custom. I think if you go back to your example cache page and look at posted coordinates they use a dot for the decimal, the example coordinates provided in the checker also use a dot, so doesn't it make sense to use a dot when you enter your solved coordinates? For me at least, this seems like a situation where it's better for the user to adapt rather than the site spending engineering time fixing what (IMHO) is a minor problem. (YMMV)

There used to be challenge caches which require people to find caches from a specific list, which changes over time, for example: https://www.geocaching.com/geocache/GC4M87N (top 20 most favourited multis in Dublin) My question is: would such a challenge still be allowed according to new challenge requirements? If not, which guideline would it break? Thanks

If you haven't already I would recommend posting this to the NoVAGO Facebook page, it gets waaaay more traffic than the regional forums here. https://www.facebook.com/groups/NoVAGO/ P.S. Thank you for addressing this BEFORE you move.

Hi all, I am going to college far away and so will be adopting out a cache. It is called "Sundials" (GC95DNM), and has 11 favorites. If you are interested, please know that its final location is not ideal, so feel free to change it and then just edit the clues (it's a multi). I'm sure there are better hiding places in Old Town that I just hadn't found. Please respond to the thread if interested. Best, CookieTheAmazingCat

Yes, that's one of the original examples that prompted my post. I found many others just in my area that are similar, different COs. It's something I wouldn't have considered myself, but seeing all the brand new users in my area immediately getting premium made me think more about it. It is fun having bogus coords in interesting spots, but if we are doing this then it should be clear that there's no reason to actually visit that spot in-person.

It's not adding another disclaimer, it's adding the first disclaimer in situations where there is none. Someone who opens the app right now and navigates to a mystery cache where there has been no disclaimer added to the description will at no point see a single disclaimer. The short term solution I proposed would take one staff member 30 minutes to implement. It only requires adding a line to the guideline page and no coding changes. As others have mentioned in this thread, because most COs are already adding this at the top of their descriptions, it should also have a very minimal impact in terms of more work for reviewers. I also don't believe it is necessary to apply this rule retroactively. It would just be a good idea moving forward. Maybe one day when there's a long term solution, but for now there are very simple changes that could be made in the short term.

The false negative is correct as coordinates always uses a decimal point. This is to avoid confusion with coordinates in CSV files (where the comma is a data seperator).

It says something about a CO who would put their mystery coordinates on a grassy knoll surrounded by highway. It would only take one determined newbie to make this go very badly. I wouldn't want to be a CO that's responsible for the potential tragedy, or for freaking out other drivers who see someone running across a highway. Maybe the CO either hasn't considered it, or maybe they think it's amusing.

You mention this issue several times in your OP. I suspect you will get some pushback from the volunteers who already put in long hours to keep this game running smoothly. I agree that many new cachers do not read the instructional materials. They just click the buttons and blindly follow the arrow. These cachers probably will not read the cache page too. I'm a late era boomer who has been playing this game for 20+ years. I have noticed that many people in younger generations prefer to crowdsource their information via social media posting when it is seemingly easier to look up the answers via Google or the help center. It's not an issue that is unique to geocaching. I see this phenomenon in several other communities I am active in. It is a generational shift in attitude and behavior. Adding another disclaimer to the cache pages won't help those people. I applaud your creative thinking but IMO you are suggesting a solution that is a problem for a very small subset of the geocaching community. I agree that parts of this game have steep learning curves, but do not feel this is one of them. New cachers face larger issues that deserve the attention and energy this project would demand. Getting accurate coords and learning about different formats would be #1. A close #2 is understanding that just because you did not find it doesn't mean it isn't there. ** I just read the latest update release from HQ and it seems they have taken some significant steps to address issue #1.

Tradicionais em Santa Catarina http://coord.info/GCAQ0G7 Multicultural I: Cemitério do Imigrante São Paulo http://coord.info/GCAQ0PQ Roda Gigante BCs!

Thanks. Yes, it was UNpinning that was broken for me, but works now.

It seems that the gcapp:// is not longer working? Is that correct? Besides of the GC-Code, is it possible to open the app at any given coordinates?