Jump to content

geoawareUSA9

Site Wide Moderators
  • Posts

    429
  • Joined

  • Last visited

Everything posted by geoawareUSA9

  1. I merged multiple threads and separate posts into this one topic.
  2. Apologies for the late reply - and English reply - but I see the souvenir in your profile, so this appears to have been resolved. The 2024 Leap Day souvenir required four finds or Adventure Lab stages completed on 29 February 2024 For anyone else, if you have completed the requirements for a souvenir and didn't receive it, contact the Help Center with details.
  3. My bad translation: Certitude is an API partner but not part of Groundspeak, so questions about their site would be best addressed by @certitude. p.s. I edited your title, I imagine you'll get more resposes if the subject title is not your geocaching name.
  4. No, it's not automatic. Caches are reviewed by human* reviewers, who typically publish a cache once it meets the guidelines. *Some reviewers are dogs. Yes, you can request the reviewer to accommodate this as part of the review process. The best way to avoid this is to go through the guidelines ahead of time, since that's what the reviewer will be using to evaluate your listing. Happy caching, and I hope your first hide goes well.
  5. What you haven't shared in this thread is that your dispute with the reviewer has since morphed to one on the rule about having a mystery cache within 3.2 km of the bogus coordinates. I would encourage you to continue to work with your reviewer. Appealing reviewer decisions to the forums is not a means of redress. The real discussion here needs to happen on the cache page between you and your reviewer, not in the forums between you and people who don't have access to the unpublished cache. Since that discussion with the reviewer is actually happening, there's no need to continue a discussion here.
  6. Please don't post in the forums looking for a puzzle solution. If I am stuck on a puzzle, I usually ask the cache owner for a hint first, followed by cachers who have recently logged it.
  7. My bad translation: It means there may be a problem with a geocache, and a geocacher has suggested that the owner check on it. Help Center article Apologies for the English response, my French is pas bon.
  8. The official app only shows traditionals and events for basic members, so challenges won't appear at all in that, regardless of D/T rating. Of course. That slipped my mind. Thank you.
  9. FWIW, I think hide-a-key containers work best when they're placed somewhere sheltered, and where any water that gets inside can drain/evaporate. The log may get damp, but then it can dry out. Adding a plastic bag just traps water, so the log gets gross. Yep. The theory is, the plastic bag keeps the log dry. Which is great until the first time the log gets damp from someone caching on a wet day, or an unsealed bag. After that, the plastic bag keeps the log wet...
  10. It's frustrating. It doesn't happen often, no, but when it's your cache, one time is too many. Without doing some sort of surveillance, we can't know if your cache was taken by a geocacher or by a muggle who thought the container was neat and swapped it for the candy container. So while it's going to be tempting to try to figure out who took it, it's going to be hard to prove. I have had the same thing happen with nice ammo cans replaced with glass jars. They also had notes inside that geocaching was littering, so I knew I had some sort of anti-cache vigilante. (Either that, or someone wanted my good containers badly enough to pretend they were an anti-cache vigilante.) My ammo cans were part of a series, and they weren't the only containers stolen, just the nicest. So the first thing I did was to remove what shoddy containers were left behind and archive those cache listings. Once a muggle or cache thief knows about a geocache, they can return. For a while, I made my subsequent hides premium member only, because I'd noticed that the higher terrain and higher difficulty caches in the area hadn't been touched - which means it was perhaps a basic member using the app. I later hid an entire series in another area about twenty minutes away, using ammo cans, but premium members only, and none were stolen. But premium members can be thieves, too. Years ago, there was a cacher arrested in Rome, NY, who was a prolific cache thief. Anyway. I am now back to having my caches available to all members. So far, so good.
  11. You've already got a couple answers about how they work, so other than linking to a help center article, I'll leave it there. Edit, forgot my links! Hide a challenge Find a challenge Astonishingly, there don't seem to be too many near where you have hidden caches, but there are many down in the Saint Louis area. The searches that you can do on geocaching.com are limited, because you're not a premium member, but you may be able to use the challenge cache map tool at project-gc (this may require project-gc membership). While any given cache might be premium member only, challenge caches as a whole are not necessarily available only to premium members. Though as a puzzle/mystery type cache, they will not show up in the official geocaching app for basic members. I don't go for all challenge caches. I love county challenges, which require finds in every county in a given state, because they give me some structure and an excuse to explore. Other challenges might focus on things I don't enjoy as much, like, "Find 50 caches with the climbing gear required attribute." I don't like heights or climbing, so I would not seek this one. But for someone who enjoys combining climbing and geocaching, this would be right up their alley. Edited to clarify that ? caches will not display in the official app for basic members.
  12. Plenty of folks use magnetic hide-a-key containers, but these are not waterproof by any stretch, so they go through a lot of plastic bags. I get pretty good results with using PET preforms (which are pretty waterproof and durable) and just gluing magnets to them.
  13. I don't see the error when I click the link, but I do get a 404 error when I try to view OP's profile. So perhaps therein lies the issue.
  14. Based on @MartyBartfast 's response, this appears to be a firmware bug with tour tablet and not a geocaching website or app issue. But it may still help the Groundspeak engineers if you provide your firmware and software versions, and specify whether you're using the website through your browser, or the official geocaching app.
  15. Moved to trackable forum. The travel bug clings one sees are generally purchased and not made, and include a TB code to be activated.
  16. It also appears some of the stats don't get updated now until you post a new log, then it all catches up. That also makes sense, and may be the more accurate answer.
  17. Could just be a latency. Check back in a day and see if your stats catch up.
  18. Merged in a related thread about missing GIF image
  19. I once found this night cache with a "reactive light" stage - when light shone on it, it lit up to reveal itself. It likely worked with some sort of light-detecting cell. I would think this better than having a flashing light going off all the time, both for battery life and for concealment. But I don't know excatly how it worked. Perhaps its last owner @Schlauwiner could shed some light (pun intended).
  20. This is already an option for premium members. If you go to the search page and select the "filters" box to the right of the search bar, "needs maintenance" is the first attribute on the list at the bottom of the filters. It also can be done with a pocket query search - if you scroll down to attributes when building a pocket query, again, "needs maintenance" is the first attribute displayed.
  21. I edited out the unauthorized app. If you need help with that one, you need to go to their forums.
  22. It seems this thread has run its course and devolved into unrelated issues.
  23. But what would you do next if your note was ignored by the CO, or the CO flat out refused to comply? I won't speak for @Keystone, but in either situation, I'd disable the cache until they responded. If they were ignoring my notes and continued to simply ignore my notes, eventually, I'd archive the cache for their failure to ensure the cache was compliant with the guidelines. If they responded but refused to comply, then I'd direct them to Appeals.
  24. If the owner hasn't responded, you can of course return to the cache where you left it, get the code, and fix this yourself. If that's not possible, leave a note on the cache page, noting the TB is there and needs to be grabbed, and on the TB page, noting the GC # of the cache where you left it.
×
×
  • Create New...