palmetto

It's an old statement. In previous iterations of the Challenges article, it was under: What makes an acceptable challenge geocache? A challenge geocache needs to appeal to, and be attainable by, a reasonable number of geocachers. A challenge geocache may not specifically exclude any segment of geocachers. --- It's never caused any problems in any review or appeal I know about. It means that your challenge cannot call out, "only cachers based in Austria", "only cachers with children", "only cachers who are members of This Facebook Group", etc. This stuff show up (rarely) and can quickly be rejected. In terms of challenges that are physically too demanding, or expensive, it's just like the rest of caching. You may not be able to, but someone can. Seems like a non-sequitur to the rest of your post? Mmm, if I saw this, I'd start with available caches, and show me who qualifies. I wouldn't really expect much trouble on either count, not in my area. This might well vary locally. In my review area, many public areas restrict dogs.

Look at GCD362 Treasure and Scavenger Hunts - for an example of a grandfathered cache that would not be published today ;-) As niraD has posted, with any cache inside, an important consideration is GPS USE. The seeker MUST load a set of coords for a discrete location (not the parking lot, and usually not an entry), necessary to the cache hunt. Multi-cache is often easiest. Coords to cache in parking area, that explain cache location inside. Ask the library first about a cache inside! they often say yes. Place a hollow book in the reference section works well. It needs to be somewhere such that the cache seeker does not have to ask staff for it. It can be a more conventional container, if the library will accommodation that For some years, reviewers were told to "loosen up" some on gps use for library caches. So there are many around that are not exactly crisp in that regard.

Also, you can see your own stats, even if you've hidden them from others by getting to them from your private profile page https://www.geocaching.com/my/statistics.aspx

I review cache pages, which gives me a particular and possibly peculiar viewpoint on the thread title and opening post. What I see is similar what I see on cache listings - it's quite possible to use a generic term, like "store", instead of naming the business and/or product. It would have been possible to discuss play and stats additions that might enhance geocaching, without referencing another game by name. (If this were a listing, I'd disable it ;-) with my minor edits log). I suspect mods here are wondering right now about how to handle this stuff in these forums. Mostly, if you want to talk about "other game", you're encouraged to use "other game" forums. (As a player, I'm personally not interested in stats levels, badges etc , or fiddling with devices while outdoors any more than I must...)

Alternately, cache from a list, that you first create via Pocket Query. That would be Traditional caches, at D and T at or lower than 1.5, and Are available to all users

IF you saved the TB Tracking codes, use those to grab TBs again, and then drop them correctly with Write Note logs to the correct caches. Most likely, you don't have the tracking codes. In that case, post a Write Note log on the TRACKABLE page, and ask the Trackable owner to "grab" the trackable, and then use Write note log to drop in the correct cache. Provide them with the correct GC Code of the cache where the trackable physically is. Most likely, nothing will happen. A few trackable owners will understand and take care of it, most will not. Eventually someone will pick up the trackables, and move them, and hopefully log properly. So this becomes a minor hiccup their life cycle.

You submitted the cache on Feb 11, and the reviewer published it with no comment or questions that same day. You may have intended to submit it as a Multi, but I'm reasonably confident that it was published exactly as submitted. It also seems correct as Mystery. The listing coords are just as the Mystery cache guideline describes, "a general reference point." And the listing coords do not meet the Multi-cache requirement, "The coordinates posted at the top of the cache listing are for the first stage of a multi-cache".

If your expectation is that I could take the info on your cache page together with the listing coords, and start and finish the cache without outside assistance, that's a Multi-cache. If at some point, I'm probably going to stop caching and start researching, or spending a large amount of time over some puzzle, that's a Mystery.

I doubt there is an average. And it would be essentially meaningless in any case. Cache submission are nearly always read within 7 days of being submitted. In many places, first reading by reviewer within 2 days. But time of submitted to publish? A large percentage of caches on first read through: need coordinate updates (coords clearly wrong), nothing useful in the original reviewer note, I need info too near existing cache listing language changes (restaurant recommendations #1 reason here, but others - for instance, must post photo, must email me) need permits or permission How long before these get fixed, edited, Submitted for Review again and get read again, and get published? highly variable. Some percentage never do, how do you average that?

You drop it into the cache like you would any other - use a Write Note log, to the cache's page, and select the TB out of your Inventory as "drop". A bit of text, "TB drop"... I went looking for your cache. I wonder if you mis-entered the additional waypoints. First, you have a FINAL waypoint as public (viewable on the listing). If that's your final, why work the formula? And it is nearly 30 miles from the listing coords? (I suspect you haven't entered the actual cache coords at all, so the cache cannot be reviewed). Your listing coords are stated as "for parking". Note that the definition of a Multi-cache states, "The coordinates posted at the top of the cache listing are for the first stage of a multi-cache".

The cache owner has posted that the cache is present. So, there's no difficulty here.

You posted Write Note logs to the trackables. This is not the procedure to mark missing. To Mark Missing, use the pull down box on the trackable page and select Mark Item Missing. To the right, click "GO" You'll have to confirm that. A pop up box will ask you to agree. https://www.geocaching.com/track/details.aspx?guid=f4d0740b-96d1-4716-9f39-adddd780f4b3 I occasionally see this action log fail. If you look at the trackable https://www.geocaching.com/track/details.aspx?guid=cd9db57d-197b-4c50-bc36-0884d481d6c9 ,you'll see a proper logged Mark Missing by Beach_hut, but the TB still shows in the cache. 08/09/2015 Beach_hut marked it as missing The log posted, so it must have been properly done.

Because a checker requirement has been disclosed, that's all that folks have to talk about. I understand that. But the new challenge cache guidelines aren't going to be, "has project-gc checker = OK". They'll be some modifications of the existing guidelines, PLUS, must have checker. Review will be as ever, starts with physical cache meets physical requirements, challenge requirements meets challenge cache guidelines, and has checker.

Moun10bike has reported this to staff

I'm not quite sure what you're asking, but the moratorium was announced as one year, beginning April 21, 2015. So its status currently is that it's been about 11 of 12 months.

The reviewer only see logs to unpublished caches when they open the cache page. Your listing was archived, so they're not opening that page, not seeing your questions. Just an FYI on process. In Florida, there are physical caches in both National Parks and National Wildlife Refuges, placed by rangers or long time volunteers. I've yet to see one that was simply placed by a local, though the Everglades National Park has said to a local cacher that they are considering allowing some caches along a hiking trail that he proposed (this consideration is into its second year, but hey - they haven't said no yet). Caches in NP or NWR are rare enough that I actually use the contact info in the required permission to reach out and make sure that the permission is real.

I agree, it would be pleasant if the driving directions were to parking. That said, most let their gps devices navigate while actually out driving around. Hopefully, they'll realize that they should load the PARKING. My player account owns a cache with this in a log, "After driving around a bit, we thought of this extremely awesome idea - putting the parking coords into the GPSr! Then we found it pretty quickly...".

I appreciate your frustration. The entire cache submission process is somewhat opaque from the hider's viewpoint. And I understand that the UK regions are not quite analogous to well defined political regions. The first sentence of the listing guidelines provides a link to the Geocaching Regional Policies wiki, where under the UK, you'd find the UK Geocaching regions map. https://wiki.Groundspeak.com/display/GEO/United+Kingdom#UnitedKingdom-ukmap Trying to provide a link to the correct page of the wiki from the cache report form after coords have been entered would be quite complex. Also, few world regions have such specialized geocaching regions. As a UK hider, you face another issue, which is being *quite* careful about E and W longitude. The report form will now likely automatically assign West longitude to anything new you submit. You might hide on both sides of Prime. As a reviewer, I can tell you that correcting location info is not time consuming. Some reviewers will simply make the correction,and explain via log to the cache page that they have. Many will not make any edits to cache pages.

Make your caches PMO for a time. Cache maggots won't pay to play. Your maggot is a Basic Member. I'd leave them disabled for a couple of weeks, before replacing and enabling again. You change the status of the cache to PMO from the edit form, it's a check box under the cache owner name field. You can go UNCHECK this in a couple of weeks or months, your local maggot will have moved on to some other form of delinquency. I'd report these users to staff (not a reviewer). http://support.Groundspeak.com/index.php?pg=request Use the Help Center contact form, and call this 16. Geocacher Disagreement.

For the map to work, you must have set home coords in your account. I suspect that many users have not done this, and would be turned off if forced to do so. I just tried it from my "no home coords" account. It comes with a pop up box offering to let me set home location, and assuming a location based upon my ISP address. The pop up can be dismissed ("not now"). The default location is Seattle WA.

I expect that staff knows that there are users who do not enter the site at Geocaching.com, but go instead directly to some bookmarked page public/private profile, PQ, map, whatever. Those people will hardly notice this change, and may not see it at all. It will impact those (more novice?) users who come to Geocaching.com. Those are the folks they're trying to track, "The intent of the test is to determine if users will benefit from having the Search page exposed during their first logged-in interaction."

A weakness of the log type. There's no text box available, you click Mark Missing and "agree", and the log posts. The text is automated. To offer an explanation, a second Write note log would need to be done. I know I rarely bother, I expect most cache owners do not either. Usually no one really knows anything, other than it's not in the cache. I agree that if cachers would routinely post notes to trackable pages, it would help the trackable owner to more quickly look at the cache page, and possibly figure out which (usually novice) cacher took the TB but did not log it.

Typically the HQ cache will have over 100 trackables in inventory. I've seen Mingo (the oldest cache in the world) with over 100 trackables in inventory. To see them all you have to click a link to a page of the rest of the trackables, there are several pages of 20 per page. There are other caches in the U.S and Europe where this kind of inventory is likely. I don't think your button on a cache page works once inventory climbs above a few trackables. It may not work once there's more than 1. In the end, the action has to happen on the affected listing - the trackable page, not the cache page. People who don't care enough to chase down the correct page, probably shouldn't be fooling with it anyway. I completely agree with this idea, or something similar, as in the other thread. Some means for the player community to get trackables into a Unknown location, and out of cache inventory. Many many trackables are missing. No one is minding that store. It's not actually a function site admins are expected to handle. It isn't really being done at all right now.

Hi KirkwoodCacheCrew, you might want to eyeball this thread on similar idea. http://forums.Groundspeak.com/GC/index.php?showtopic=284690 If any such thing is to be done, it should be on the Trackable page, not on a cache page. Site admins can post a Mark Missing log on trackables. That log automatically generates an email. But no one is "having to email owners".

https://www.geocaching.com/hide/report.aspx?guid=f1d3b703-bc6b-4fb4-88a1-daec145ff398 Link above for the edit page on your event. This can be built with the guid, which you supplied. I can see the edit page, but I'm reluctant to fool with it. Only cache owner will be able to make use of this link. If this listing were mine, I'd kill ALL the html, and have plain text. We are some people of the organisation team of GeoNord 2016 Mega Event and we are spending some days in the area to attend the Hoorn Cache Mega Event and we want to meet some local or international geocachers. It's a good time to meet other geocachers and share some geocaching adventures or to share where are the most amazing places, but most of all, to taste some good chese or beers! From 8:00 p.m to 9:00 p.m (AT NIGHT AFTER THE HOORNS MEGA EVENT) See if making that change works. If it does, great. If not, then staff will have to intervene. I note some html that I've never seen before, what's a "widow"? "widows:1"