geoawareUSA9

I'm not sure about "maintain the caches' inventories", but the ability to mark as missing is certainly a help to the TBs' owners since the CO is the only one can objectively identify if a cache is missing and does not have relevant TBs in its possession. I'd say it's a helpful final punctuation ability that the CO has; but it's not their responsibility (in the strictest sense, not sure if the word appears in the guidelines :P) because they have no control over who "drops" TBs into the container. I think it's similar in obligation to maintaining the integrity of their caches' log history. Anyone can post any log at any time, so no one should expect that the log history is going to be 100% accurate 24/7. And clearly it's not a responsibility to the point that if a false log is reported the CO will immediately see consequences. It's more like, the CO has the ability and it's in good spirit to make use of that ability for the sake of the community - ensuring Find logs are consistent with finders' signatures, plus other log types, and TB logs. It's better for the community, but not a required obligation. That's how I understand it at least. I tried to stay away from stating or implying that keeping track of the TBs in a cache is a cache owner responsibility or obligation. That's why I used the word prerogative, as in, if a CO wants to cull a missing TB from the inventory of one of their caches, they have the ability to do so, just as the TB owner does.

If that were the case, then cache owners wouldn't have the ability to mark TBs missing from their caches' inventories. It might not be your concern, but it's within a cache owner's prerogative to maintain their caches' inventories.

Sure, because none of those things were in your control, so it's not really helpful discussing them with you. On the other hand, leaving false TB logs (with the increasingly ironically titled "Honest Loggers Coin") was entirely within your control, as was your letting the TB sit in cache inventories for a month or more for your convenience. I'll leave you to your devices, with one last thought: If what you're doing is OK, then it'd be OK if everyone "dropped" a TB in a cache every time they felt like it without actually leaving it behind, then left it there until they felt like "moving" it to another geocache, right? And then we'd never have to worry about whether cache inventories was correct, because we'd know for sure that they were not.

Yes, I think most people would conclude that logging finds on caches you've never seen would be inappropriate, regardless of whether you had someone sign them for you.

If it's dropped off and picked up again, the TB won't stay long in the DNF cache. Only as long as it takes to make the second log. If that was what @little-leggs was doing, it wouldn't be an issue, and I would only have suggested visiting as a matter of convenience to him as the coin's owner. If you look at the TB's history, though, he lets it sit in each cache until his next DNF happens, and that's problematic, because it's not in the cache it purports to be in. For example, it was in the inventory for GC69HDQ from 30 July to 24 August. Prior to that, it was in the inventory of GCA8TK1 for a month.

Sure they do. Here's the map for my volunteer badge, which I have only ever visited to events. The trackable inventory of a cache should be accurate. You're "dropping" a coin into the inventory of a cache you didn't find, when the coin never leave your possession, and there is an easier option that requires no follow-up log for you to pick it up again. It doesn't make a lot of sense. I could argue that leaving misleading logs is against the terms of use. "2.4.4 You agree not to ... Interfere or attempt to interfere with the proper working of our services." Logging that a trackable is in a cache when you know it's not, arguably is against the proper working of the cache inventory. I could also point to this section of the Help Center on trackable etiquette: I usually hope it's accurate, because as a player, I enjoy finding trackables. I certainly don't expect anyone to be purposely indicating a coin is there when it's not, which is exactly what you're doing. I won't stop you from doing it. But your explanation is nonsensical. Edit to add, it's also fairly ironic that your motto for this coin is that you're an "honest logger" ... when you're not dropping the coin in the caches you claim to be dropping it in.

I'm not here to tell you how to manage your travel bugs, but looking at the history, it appears you pick this up and drop it off in every cache you DNF. That's twice as much work than simply keeping it in your inventory and choosing the option to only visit it, which is what you should be doing when you take a TB to a geocache but take it with you when you leave. Example: That would also avoid the confusion that's potentially created when someone DOES find the cache you DNF'd and wonders why your coin isn't in the inventory. Because currently, GCA1E4A purports to have your coin inside it. Which would be impossible, since you didn't find it.

It's not. I'm merging this in with the existing Wheel of CHallenges thread.

No, it won't. It definitely won't. Not by itself. Owner inaction on a potentially missing or unmaintained cache is the reason for a cache being archived. DNFs lower cache health score. But CHS only triggers reviewer involvement. If a cache has an active owner, then I don't necessarily need the owner to spring into action 5 seconds after getting a DNF or needs owner (or reviewer) action or indication of a low health score. I need a response to show they are aware of the situation and have a plan to deal with it. If an owner is ignoring indications that a cache needs action, or has left the game, that's what gets caches archived.

All of the ones published after this section was added to the guidelines should. Like most guideline changes, this was not retroactive, so not all caches that existed at the time comply. I've tried to update most of our older ones so they're compliant with current guidelines, but for some, I've not had a chance to return and develop good on-site tasks. One was overly dependent on a sign, which faded to illegibility, so it had to go.

There are some existing earthcaches in the area, and others are pending review. Here's one: https://coord.info/GCABYN6 An easy way to see what's there is to go to the map view and zoom in to the area.

Without the owner's consent, no, you cannot forcibly adopt a cache. You can help maintain it. Or if it needs to go, bring it to the reviewers attention, let it get archived, and then hide your.own cache. Or, third option, do nothing and let events proceed as they will. But no, you cannot just adopt it.

I previously, and erroneously, stated that iCaching is not an API partner. I was wrong - they are. My apologies for any confusion I may have caused.

I merged in some duplicate topics.

It sounds like you have your phone set up to tag your location when it takes a photo. How to turn off geolocation on an iPhone How to turn off geolocation on Android

Someone else might have another suggestion, but I would think that this could be done by loading a large amount of caches into GSAK and then sorting or searching by latitude. You can also search your finds to see what you already have. See example screenshot: here are two caches I've found at the same latitude.

Unfortunately this is not a feature on Geocaching.com. Only one player can edit a given list (its creator). That's true. One way to get close, however, is for one cacher to start a bookmark list and make it public or shareable, and then the other cacher can copy all of those caches to their own public or shareable bookmark list, or make a pocket query based on the first list.

Not really, no. I still have a Garmin GPSr, but I only seem to use it when hiding a cache, for its ability to average a location. Mine does. But the best way to find out if it works for you is for you to download the free app and give it a go.

Moved to the GPS forum. I hadn't realized how odd the plug was until I saw your post. If Magellan isn't selling them anymore, and no one here has one they wish to part with, eBay might be your best bet. (I have no link to the seller, it's just what I found after a quick search.)

This does beg the question, if you can't maintain it, why do you want to hide it? Alternatively, you can place an earthcache, which would not ordinarily require maintenance.

Merging duplicate topic.

Ouch. It appears I have been demoted.

Moved to Creating Adventures forum.

This seems like a good time to remind folks that many parks, including one in New South Wales besides just National Parks, have policies that require permission for placing geocaches. It's usually best practice to check the local wiki to see if such a policy is in place before placing a hide.

All geocaches already come with a disclaimer, so you could point them to that. https://www.geocaching.com/about/disclaimer.aspx The first line is basically a general disclaimer of liability. "Cache seekers assume all risks involved in seeking a cache." Otherwise, other than putting your own little blurb on the cache description, you are correct, the nature of Geocaching is such that a liability waiver is going to be impractical.