Jump to content


+Premium Members
  • Posts

  • Joined

  • Last visited

Everything posted by nextlogicalstep

  1. Having cached in both British Columbia and Nova Scotia, I'd say there are some pretty big differences in what's allowed. I'm not bothered by the inconsistency, because it makes sense that something could easily cause problems here, where there are many active cachers, while the same thing might easily never cause a problem in NS, where there are far fewer active cachers. I did once have a reviewer threaten me with a $10000 mischief fine for a cache on public property that the reviewer thought would encourage people to bother nearby residents. The concern was that it was in a residential area. I didn't bother trying to go forward with that cache, and being told I was responsible for any and all actions of other cachers not necessary to find the cache was enough to put me off caching, until GS reluctantly agreed that no, what the reviewer had said was not valid. Just recently, another cacher had a cache published at that same location, so I guess there wasn't any real issue. A different reviewer published the cache than the one who rejected mine. I have had some caches rejected for reasons that I hadn't thought of - for example, one I hid in a city park was rejected for being too close to a school, when the school was a block or two away, with a building, a parking lot, and a fence in between such that the cache area was not visible from the school. I don't know if I even noticed the school at first when I hid the cache. I had noticed the spot because I had visited it months before to find a cache that was eventually archived. When I provided more info, the reviewer was fine with it. So no complaints there!
  2. That feature isn't currently available. I would recommend sticking with Certitude or Geochecker if you want that information. This is precisely why I haven't used the built-in checker for any of my caches.
  3. If I'm confident there is in fact a problem, I wouldn't hesitate to post a NM. Typically I don't check back to see what happens after that, but if I did notice that the issue hadn't been resolved and a month or more had passed, I'd probably log NA, assuming the problem with the cache wasn't just something minor like a wet or full log sheet. As a cache owner, I do not at all mind when people log NM. I don't think cachers should be afraid to log NM. Some COs will read all logs and others won't, so problems mentioned in logs without anyone ever posting a NM can easily be missed by even a responsive CO.
  4. I'll typically skip caches with a series of DNFs (or at least read the logs to see what's up before attempting the cache), but might not even notice the red wrench. I suspect most people who cache with the app wouldn't notice.
  5. The people I know who orienteer don't use a compass for orienteering either! Strictly map reading.
  6. I do like that cachers won't be forced to pay for premium to be able to access caches in the app, but I wouldn't mind if there were a restriction with a way of getting past it other than paying for premium. For example, perhaps a cacher could be restricted to 1.5 D/T until they've found a set number of caches - 20? 30? Of course, if the whole point of the restriction is to force people to pay for premium, well, I wonder how many fewer people would if they weren't forced to.
  7. You could maybe do a magnetic inside or underneath if there's a place where it wouldn't be visible. For example, it could go inside above the door. One in my city has a fake book chained in place and padlocked shut. The key for the padlock hangs on a hook on the underside of the library.
  8. Saturation, maybe? I was curious, so I ran some PQs to get stats for my area. I used a 25km radius from my home coordinates in Vancouver, BC. I excluded event caches, although I don't suppose that would make much difference. It would be interesting to see how many caches were published including those that have since been archived. I would expect the farther back you go, the more caches have been archived. 2017: 242 2016: 250 2015: 312 2014: 443 2013: 404 2012: 482 2011: 354 2010: 333 2009: 166 2008: 118 2007: 81 2006: 83 2005: 95 2004: 37 2003: 21 2002: 15 2001: 7 This is my first year caching. 22 of the 2017 hides are mine.
  9. I still don't get what you're on about, but it seems likely I never will... It sounds like you don't want checkers for anything.
  10. I like to look at the stats for what solutions have been tried on my mystery caches and number of correct vs incorrect solutions. I haven't yet had a reviewer use the geochecker.
  11. I own two multis where the cacher has to visit a location or a few locations to look for information. For one, the cacher has to go look at a bunch of murals and count objects within the murals. I added a checker after someone requested one. There's no mystery at all, there's nothing to solve, but someone asked for a geochecker.
  12. Will there be any ability for cache owners to see what solutions have been attempted? Or even basic stats like number of correct solutions and incorrect solutions? If not, I'll stick to using third-party ones that can provide that. That said, I'm happy to see this feature be added. In response to the request to make it mandatory, I think that's very much unreasonable. It's not something that's applicable to all caches of this type. Although I use geocheckers for my own mystery caches, the ones I've found relied on solutions others than coordinates. I've also seen a lot of mystery caches with multiple choice questions where there are only three possible answers. You wouldn't even have to make a real attempt to answer the questions if having a geochecker were mandatory, as you could just try them all. Why make a new feature mandatory that would ruin existing caches that have nothing wrong with them? If you don't like a cache, you always have the option of simply not going after it. There are lots of caches that I've decided are not for me.
  13. Geocaching for me often is a solitary activity. I have no problem with that. You could try inviting friends who aren't already cachers to try it with you.
  14. Although basic members can log PMO caches found with a premium member, there may be times when you want to search for only PMO or non-PMO caches. To do this, start at the search page and click "filters". On the right, the fourth one down allows you to select "Premium", "All", or "Basic" (non-PMO). Another handy filter for planning caching with others is the "Not found by" field, where you can type in usernames to see caches that haven't been found by those people. You can type in up to five usernames.
  15. For that one, I went with 4 because the guidelines mention needing "special knowledge" but then they also mention "advanced preparation", which I figure kind of applies to all puzzle caches. I guess the geochecker figures should also help - so far the correct coordinates have been submitted 8 times, versus 21 for incorrect. Ten of those incorrect ones have been close enough to find the cache though, if they went and looked.
  16. I've recently started creating puzzle caches and I'm having a hard time wrapping my head around how to rate the difficulty. It's always a bit of a challenge to judge the difficulty of something when you're the one making it, but I'm finding it particularly challenging for mystery/puzzle caches. Any advice? My first cache of this type is GC7D36C, in case anyone would like to use it as an example to discuss difficulty rating.
  17. There's also a separate section of the forums for them. You'll find lots of info there.
  18. If you didn't find the cache, how could the TB have visited it?
  19. I don't usually worry about being stealthy once I've got the cache in hand. I figure it's more the retrieving, searching, and replacing that look suspicious. It depends on the location, though, I suppose, and perhaps also the cache container. People don't seem to be all that interested in what I'm doing when I'm holding a container or writing something on a piece of paper. I live in a large city and mostly cache in the city (so urban caching + caching in larger forested parks). As a cache owner, I try to pick spots where it's possible to search without being in full view of anyone who might be around.
  20. I recently planned out a multi-cache but then decided it would be better to wait until November to have it published, as it's based on a mural that relates to veterans and I'd like to have it published in November, closer to Remembrance Day. If I want a cache to be published on a specific day, how far in advance should I submit it? (In this case, it doesn't actually need to be a specific day, I just don't want it to be until after Halloween and I'd like it to be before Remembrance Day.) Is there such a thing as submitting it too far in advance? Is it easier for the reviewer if I wait until a certain number of days before I'd like the cache to be published? Thanks.
  21. I prefer to log on the go. Occasionally, I'll go back and edit to add more detail if I think of something I left out.
  22. What I can't understand is why anyone would want to "discover" a bunch of trackables they hadn't actually discovered, let alone pay money to do so...
  23. Ah, you have to be using the Leaflet maps rather than Google. I changed my map preferences and got it to work. It seems you can't have it so that it automatically adds the circle around caches, but you can pick spots and then see if any caches are too close. Not quite what I was hoping for, but still useful. Is there a way to make the circles go away once you've created them? Thanks.
  • Create New...