Forum Replies Created
-
AuthorPosts
-
Some of these requirements are never enforced (like slope rules). They put these in as a catch all. This policy used to read exactly like the Milwaukee county policy, but we got them to change some of the more annoying requirements and language.
OK, here we go.
1 mile – 24 caches, 0 unfound
5 miles – 98 caches, 1 unfound (It is disabled. Curse you, Jerry’s dad! )
10 miles – 270 caches, 23 unfound
20 miles – 1114 caches, 178 unfound
30 miles – 2769 caches, 1131 unfound
50 miles – 5732 caches, 3930 unfoundThis may not be it, but make sure you are logged in, and then type quick. I have been having to relog on fairly often.
Basically, the answer is “it depends”. More specifically, it depends on the type of property. State parks and RA are really quick, usually they turn them around in a day or two, so you are only waiting on the mail. State forests are slower, but they usually get around to it in a month or so. State trails depend on the trail manager. But things like wildlife areas, fisheries, boat launches, and other miscellaneous properties, I wouldn’t hold my breath waiting for a reply. Of the three caches I have placed in this type of area, the turnaround was 18 months, 3 years, and, well, never.
Right answer to the wrong question. I think he is trying to get it available in a PQ so that he can download in the field using a mobile device. The funny thing is that there is functionality on the site for uploading PQs to gc.com. Works good. The only problem is that the program (Iphone app) that is supposed to download them doesn’t work. Regular pocket queries download to the Iphone just fine. When I last talked to Josh about this (I have been a pretty annoying complainer about this bug), he told me they had it working for about a week, and then the latest Iphone software upgrade broke it again. Ack!
Actually the hike for “film can” is not very far, maybe 3/4 mile round trip. Don’t make the mistakes I made the first time I went, which include:
Taking the horse trail instead of the hiking trail, resulting in a .2 mile bushwack up a 40° slope
Not reading the cache page to realize the first stage is a virtual and spending 45 minutes looking for a container (including time spent looking under the object used for the calculations)
Once you get to the final, your work will not be over. You will see when you get there. I would say allow around an hour for this one, in and out. There is not LOTS of bushwacking. Stage one is on the trail. Stage 2 involves about a 200 foot bushwack through typical KM terrain (= thorns.) If you are still looking for more after you are done, you can find Field of Pines and Iced Cache #2(?) on the same trail system, and Square Old Man is close by. There are many other “Golden Oldie” caches in this area, hidden in the days before micro-spew and parking lot hides.
Note that Rebus and Tutthead does not require any puzzles to be solved at home, but it is fairly long, involving field solves of several puzzles, and you do need to bring the cache page with you, in one form or another.
There is a macro to generate a bookmark list from GSAK. It is pretty fast, but takes a lot of clicking. I believe it comes with the installation package, and is called bookmark.gsk (go figure!) It does the entire list, but you have to do two clicks for each cache.
When caches are reported missing, we look for a number of DNFs proportionate to the difficulty of the cache. (Yes, Jim, 1 is a number, but not the number we are looking for.) Since certain people don’t feel the obligation of posting their DNFs, sometimes this process takes a long time. It also screws things up when people post false find logs “because they were in the area and looked for a long time” because I might not notice that the log is bogus. There is also a time component, so if there are 10 DNFs in a day, I’m not going to jump on the cache owner. I try to give at least a month after the first DNF for the owner to take some action. I find that most responsible owners will at least post a note within a week of a DNF.
As far as the typical maintenance problems go, I look for inaction over an extended period. It always amazes me when people ignore “wet log” complaints for 6 months, then get offended when someone calls them on it.
Notice that “close” isn’t defined. (Took me a while to figure out what you were referring to.) This is one of those point where we would have liked to help them with the wording. The “burial” language is very similar to that on the geocaching.com guidelines.
When you are dealing with prolonged exposure to a neurotoxin, the concentration is irrelevant. There are studies linking low dose, high frequency exposure to Parkinson’s disease. Up to you whether you want to risk it.
As someone who deals with this chemical on a daily basis, I can tell you that exposure to this is very serious. Anyone handling this in our facility is required to wear impermeable gloves, a rubber apron, and a face shield. In the event of a spill or other major chance for exposure, people are required to wear full body protective clothing. Anyone getting exposed to this, despite the precautions, is immediately sent to the clinic for observation and testing.
As you might guess, I won’t use this or allow it to be used by any of my loved ones.
@huffinpuffin2 wrote:
@cheezehead wrote:
I think the Permanone works!
That’s contains the serious stuff, Permethrin, and should KILL ticks on contact, with a good dose. We’ve not made that move yet, as it’s a bit on the nasty side for our recreational use. Label warnings are sobering; can sicken pets, etc. ➡ We use DEET, which is ‘just’ a repellent………and duct tape when we’re ‘going in there.’
We were caching north and east of sloughfoot’s locations yesterday, and we only got one………50! YOW! 😯 😯 We’d still be feeling them! Any of them deer ticks?
For those who want to “unlike” a cache, just click the like button again and it will undo it. Hopefully they will clarify that on some future update.
Repeatedly posting false logs to the same cache is consider harassment of the cache owner and is a violation of the terms of service of geocaching.com. If you feel this is happening to one of your caches, please contact a reviewer or email Groundspeak with the details and the problem will be “handled with extreme prejudice.”
@HeliDood wrote:
@Walkingadventure wrote:
I see you can now “like” caches for Facebook and nominate caches for the Lost and Found. Is this a good thing?
I just saw that. I think it’s pretty stupid. 🙄
One feature that is commonly requested is a rating system for caches. GS has always shied away from this idea, based on the fear that people would retaliate against their “enemy’s” caches. You can think of this “like” system as a weak excuse for a rating system. Eventually, you will probably be able to see how many times a cache was “liked” and thus have some sort of filter for selecting which cache you might want to look for.
Note that this is similar to a suggestion several people made, where people would be assigned a number of “likes” based on the number of finds they had, which they could in turn assign to other people’s caches. Maybe something like 1 like for every 50 or 100 finds. This way, if someone posted a like on a cache, it would really mean something. Now, you can just “like” every cache you find (maybe every cache period) so the ratings will carry less meaning. For now, we will just need to wait and see how this version works out.
The other advantage to using GSAK (rather than just Drag and Drop) is that GSAK allows you to use “corrected coordinates” for mystery caches (as well as for those caches where the knucklehead owners won’t fix bad coordinates). Obviously the raw pocket query data from gc.com won’t have the right coordinates for the puzzles. Additionally, if you add notes to the cache in GSAK, it will show up in your Oregon as the first log.
And yes, you can also export a GPX from GSAK and drag that file, but that takes a few more steps with no advantages.
-
AuthorPosts
