Forum Replies Created
-
AuthorPosts
-
Idling
That’s only on the caches we can’t fit the Suburban down the trails on. It can mow down anything up to 3 inches in diameter, and climb over anything up to and including Spotted Owl in size. Anything more rugged we get out and walk…
quote:
Originally posted by kbraband:
Let me add that if you HAVE found more than 100 caches, you’re not damaging the environment as long as your average number of finds is not more than 10.7 per month. (I believe that’s the official number from the EPA.)
Great, just great…
Not only are we over 100, AND drive a Suburban…
Our average is 15.4 per month! Now we’re really in trouble!
Hmmm…
We’ve found 123 caches, AND drive a Suburban!
[This message has been edited by CacheCows (edited March 19, 2002).]
All I can say is that I’ve been waiting and looking for one of ‘these’ caches since about the time we started caching. Heard about them, but never seen one. SInce this was a ‘tricky’ and ‘hard’ cache, I figured maybe my day had come, so I checked it out… and there it was!
Sorry, guess my question seemed rather odd.
I had heard of an outfitters called the ‘North Wall’, and I was hoping that your ‘North Wall’ was perhaps one of these.
A new camping/hiking type place in Milwaukee would have been excellent.
As a curtesy, you should e-Mail the Travel Bug’s owner so they will expect the delay. They should be fine with that…
What is the North Wall?
One other change made at the same time. Ever notice how some folks just can’t seem to get logging a cache right? They want to make a note, but log it as a find? Or say they didn’t find it, yet the icon shows a find?
Well, most of these errors were from the log type being a drop down box that defaulted to ‘Found It’, and folks not knowing what a drop down box was or how to operate it.
Well, the drop down box is gone now, replaced with three radio buttons. The default is still ‘Found It!’, but this should help reduce the errors.
I’ve also asked Jeremy to add an additional log feature. If a cache is tagged as containing at least one Travel Bug (TB), then when a cacher logs that cache, they will be prompted for if they retrieved that TB or not, and if they did, it will direct them to log the retrieval. This should help reduce the mis-understandings on how TBs work. The process is less than intuitive (you log the retreival on the TB’s page, but log the dropp off on the cache page, and if you dropped off the TB before logging it, your up the creek unless you wrote down its ID number).
[This message has been edited by CacheCows (edited March 13, 2002).]
Yes, Jeremy’s banners will work fine as there is no JS involved…
Yes, Jeremy did that a couple hours after I came up with the ‘onload’ workaround. Those of us that got it installed before Jeremy implemented his java-script censor are sort of ‘grandfathered’. Our code will work untill we need to edit our cache pages, then, as you discovered, we will have to remove the JS code.
Its just that reason that has me waiting on updating anything. BTW, over two weeks ago when Jeremy first shut down JS, he promised to increase our long description space (many of us were using JS to include long descriptions from off site include files). I’ve been e-Mailing him on a weekly basis to remind him, but he has yet to make good on his promise. In the mean time, my Beulah Cache sits briken as most of the text is no longer there…
Ditto on the great job Steve!
We’re hopping to make a stab at it ourselves this week if time permits, it sounds like a blast of a hunt!
[This message has been edited by CacheCows (edited March 12, 2002).]
yeah, apparently no one had a picture from NHO at the time of the story being written. Note that the text under the picture says its from a recent hunt, not from hunting NHO. The article was written very shortly after the cache went up…
If you heard or read the story, you probably heard the reporter mention that placing a cache in any National Park (or National Monument site) is illegal. Just in case you were not aware of this rule, its been around for quite some time. he J-Man has had it posted on geocaching.com on the page that explains how to create a cache. I’ll quote it here for reference:
- Will it be on private or public land?
– If you place it on private land, please ask permission before putting it there! If you place the cache on public lands you need to contact the managing agency to find out about their rules. You will be in violation of federal regulation by placing a cache in any area administered by the National Park Service (US). The National Park regulations are intended to protect the fragile environment, and historical and cultural areas found in the parks.
quote:
Originally posted by lizs:
(Now am I to take it that the Jeremy who runs http://www.geocaching.com is also the Jeremy who posts here?)
Hi lizs, and welcome to geocaching and to WGA. We too hope you can make it to the campout.
FYI, the Jeremy that runs geocaching.com and the Jeremy that posts here are not one in the same. Hence, to keep confusion to a minimum, we usually refer to the former as the J-Man and the latter as Jeremy.
Just learned of another great feature given to Members:
Members can now temporarily disable their caches, and then re-enable them on their own. So if you are working on your cache, you can let folks know not to hunt it.
Click HERE and scroll to the bottom of the screen to see what a disabled cache looks like on the serach pages.
Then click on my Beulah Land cache to see it in action.
-
AuthorPosts
