Jump to content

AdventureRat

+Premium Members
  • Posts

    65
  • Joined

  • Last visited

Everything posted by AdventureRat

  1. I have noticed this problem for quite some time, but was only recently able to identify the exact conditions that reproduce the problem. I have a test pocket query that only specifies "Countries" (Canada), "From Origin" (My Home Coordinates), and "Within radius of" (1 km). When I run this query, it displays the correct four caches in the list. Now if I edit the query and change 1 km to 2 kms, press "Submit information", and then run the query again, I get the same list of four caches instead of the ten that should be in the list. If I edit the query again, it still shows 1 km instead of 2 kms. Now, if I change "Within" from Canada to None Selected, and then change 1 km to 2 kms, the query is updated correctly and displays the correct results when run. As I mentioned, this is a test query to simplify the number of variables involved. The actual queries that I run specify many more criteria, but none of them seem to affect the updating of the "Within radius of" value. This is more of an inconvenience than a serious problem, but it does seem to be a bug. I live right across Lake Ontario from the state of New York and am not really interested in having any New York caches returned in my PQs, hence the Canada requirement. Has anyone else experienced a similar problem, and more importantly, can someone from Groundspeak comment on this? Thanks.
  2. Yes, I've run into a similar problem. I have a PQ that selects all of my unfound caches within the 500 closest active caches to my home. Obviously this is a moving target as it's affected by both newly published and archived caches, as well as the disabling and enabling of caches. Whenever I attempt to edit this query to adjust the "Within radius of" amount, it always reverts back to the original value after I save it.
  3. 3:30 PM and no sign of the three pocket queries that I run every Monday and Thursday. Their usual arrival time is a ten minute span around 10 AM. My Sunday pocket query never did run. It might be nice for someone from Groundspeak to toss us some kind of explanatory bone.
  4. Wow? It's hard to believe that you're shocked at the general reaction to your comments. Based upon your "hands on" approach to this issue, I would have a difficult time believing any documentation that C/A might provide of the proper authorities approving of his cache placement would be accepted by you. In my mind, you contacting the authorities is the only way you would ever believe what they said, but since you refuse to do that, I don't believe that the authorities could even sway you from your beliefs. I'm very curious to hear your response.
  5. Try submitting your cache listing for review ahead of time and only include some general details and fake coordinates. Explain in the reviewer comments the true nature of what you are trying to accomplish, and provide whatever other details the reviewer requires in order to properly evaluate the listing. After the listing is published, you can update it with the proper information at the designated time. Don't forget to include information about when the listing will be updated in your original publication. I've seen this method used effectively for a number of event related caches and cache series, as well as holiday themed caches for things like Easter and Halloween. It takes the onus for providing the information in a timely manner off of the reviewer and places it onto the cache owner, but at least it gives you the element of timing control that you desire.
  6. The responding timely aspect should include disabling your cache if there's a reasonable chance that something is wrong, such as having been muggled. Reasonable chance is something you'll have to figure out for yourself as you go along. I wouldn't be concerned about one or two DNFs by newbie cachers, but more than one DNF by experienced cachers would get me to disable one of mine until I took a look myself. Of course a note from a previous finder saying it's not there would probably do it too!
  7. Oh yeah, I forgot one thing. Use your Ignore List. If you find a cache popping up in your pocket queries that you would never find because: 1) it has a puzzle you'll never solve or don't want to solve 2) it's too physically demanding 3) it offends you in some way 4) you don't find it worthy of your effort 5) you don't like the cache owner 6) whatever else ... put it on your ignore list. It's not a bad thing, it's what it's there for. Use it!
  8. Okay, at BBoG's request, I'll chuck in my $30 worth. First off, here's what I consider to be the inalienable rights of every geocacher: 1) Within the posted Geocaching.com guidelines, hide what you will, where you will. 2) Feel free to wrap a mind-numbingly difficult puzzle around a cache. 3) Construct a 30 stage multi that spans two provinces, if you like. 4) Like or dislike any cache, for any reason. Now to answer Barnie's question, no, you're not the only one yearning for "a peanut butter jar wrapped in camo tape". That's my ideal end to a geocaching adventure as well, but, I do like puzzles. I've solved thousands of them since I was a kid, and I continue to enjoy solving them now. I don't mind learning a little about an obscure topic, or an interest that someone else has, but I don't want to have to become an expert in the field in order to solve a puzzle to find a cache. A puzzle should add something to the entire experience, such as teaching you something about Braille, or force you to finally learn how to project a waypoint with your GPS. It shouldn't be put there JUST to make finding the cache more difficult or time consuming. As for micros, I would prefer that folks not use them as the final container for puzzle caches. If you have to use a micro because of the location, then pick another spot. And as far as locations are concerned, I agree with BQ 100%. When you're looking for a place to hide a cache, please ask yourself "Why here?", and if you can't come up with a decent reason, that's not the spot. And if the spot has considerable tree cover and poor satellite reception, that's not the spot for a micro either. Consider a small cache with a clever hiding spot or some super-effective camo. I don't believe in increasing the difficulty by decreasing the container size, especially in the woods. Just remember, these are only my preferences. It doesn't mean that I won't try and solve your puzzle or find your cache if it isn't my dream cache. You should be able to tell by my log entry whether it's thumbs up or thumbs down ... for ME.
  9. I seem to be unable to successfully save changes to the "Within radius of" value specified in any of my pocket queries. I modify the value and select the "Submit information" button, and then I receive the message "Thanks! Your query has been modified You can preview the search on the nearest cache page." However, when I return to the "My Pocket Queries" page and edit the query again, the original value is displayed. I currently have 23 pocket queries saved, but many are only run online, and no more than three are scheduled to run on any given day. I am running Windows XP Professional Service Pack 2 Build 2600 and Internet Explorer 6.0.2900.2180. Is anyone else having a similar problem?
  10. I'm seeing quite a delay from my normal pocket query run times as well. I have three queries that run every Monday and Thursday, and I usually receive the results shortly before 8:30 AM ET. Monday of this week was fine, but none of the queries has run yet today. Is anyone else seeing the same delay? Also, it seems that the sending email address for PQs has changed from contact@geocaching.com to noreply@Groundspeak.com.
  11. I'm looking forward to this year's event, in whatever form it may take. Flash Finder may even join me this time, and he brings his own flavour of enthusiasm. No subpoena for me yet , but I'm up for the courthouse event cache. Gee, I wonder what I can get Tequila involved in this year.
  12. I don't know what it's like in your area, but our reviewers seem to be doing this already. Caches with Needs Maint or that have been disabled for too long get a reviewer note prompting the owner to take action. If no action is taken, the cache gets archived. -eP I think that the cache reviewers do a great job, and I am thankful for their tireless efforts, but ... things still get missed. The "Needs maintenance" attribute has been set since August on one cache listing near my house, and on another since March. Neither listing has had a reviewer note posted. Also, there is a multi-cache nearby that has been disabled because of a missing stage since September, also with no reviewer note posted since then. All three have resulted in disappointing cache experiences for visitors. This is why I'd like to see some automation of the review process with known acceptable limits on "Needs maintenance" and cache disabling.
  13. "The hike to the cache exercises the body, while the solving of puzzles exercises the mind." AdventureRat - December, 2006 For those that do not enjoy solving puzzles or researching various topics, many have pointed out that the ignore list is there for a reason. Please feel free to use it as you see fit. Do not eliminate an aspect of the game that many of us find extremely enjoyable. Broken links on external pages required to solve a puzzle shouldn't be treated any differently than damaged stages or potentially muggled or missing cache containers. Needs maintenance log entries should be posted, and prompt replies and action should be taken (and required) by cache owners to ensure quality caching experiences for all. Here are a couple of suggestions: 1) Run a daily process that disables any cache listings where the "Needs maintenance" attribute has been set for longer than one month. 2) Have cache reviewers allow cache owners less time for response and action on cache issues, and archive caches much sooner than six months (which seems to be the going rate) after seeing no action. The real thrust of this should be to place more onus and responsibility on cache owners to maintain their caches, be it the physical containers or the cache information. Whatever you do, keep puzzle caches alive !!!
  14. Geocaching is supposed to be fun. If you place too many restrictions on logging a find, and combine that with making the cache ultra difficult, you won't find many people even making an attempt. Since you want people to find every stage, does that mean if I go out caching with two friends, and one of them finds a particular stage, I can never log a find because I can now never find that stage on my own? If I can still log a find, what's the difference between this and someone who's completed the cache before, providing me with the location of one of the stages? The cache description has now been updated to say that the final will be moved once a month, presumably to prevent finders from providing any help to others. I wonder what cache-tech will think about you updating the final coordinates every 30 days. I'm in the middle of doing this cache. I've found both the first and second stages, and have not even made an attempt to find stage three. I'll wait to see how all this plays out to decide whether to continue, or place this cache on my ignore list. AdventureRat
  15. For me, geocaching has provided an entertaining opportunity for exercise (both for the mind and the body), a reason to go places I wouldn't normally have gone, and a sport that I could enjoy with my whole family. The surprise benefit was being exposed to a great community of people with some similar interests. Tony is one of those people. I had the pleasure of caching twice with Tony, the first time at TOMTEC's Excellent Midnight Adventure! back in January when Tequila conscripted him for the IT Guys, and again when we tackled The Big Pipe series as part of Geofellas' April Fool festivities. His type of wit fit in well with my own, and his easy going and friendly nature made it seem like I'd known him for years. I just wish that I had known him for years. He also garnered a respect like no one else. I have heard many people speak of seeking out Tony for advice on different things. I have also noticed that many geocachers (myself included) reason that if Tony had a difficult time finding a cache or solving a puzzle, then it was okay to have a difficult time or fail ourselves. Being viewed as the measuring stick for success is one of the ultimate signs of respect. I wish Sue a speedy recovery, and the whole Dawe family the best in the future. Tony, we'll all miss you. Larry "AdventureRat"
×
×
  • Create New...