Jump to content

CacheCows

+Charter Members
  • Posts

    177
  • Joined

  • Last visited

Everything posted by CacheCows

  1. I've been away from these forums for quite awhile now, and am saddened to see that the reason I left, a general lack of graciousness, still prevails. The cache Tunnel of Terror is actually the second cache at this hiding spot. I hunted the original cache located here, and can vouch for the fact that there is indeed a posted sign at the trail head that the trail is closed. Like many, I chose to disregard the sign and hunted the cache anyway. I was in the wrong for doing so, I admit it. Was the cache dangerous? No, but had I entered the nearby tunnel, that look oh so inviting, there was danger, and with it a liability to the property owners, and hence the reason for the entire trail being closed. So, Manager stated a true fact: the Wisconsin State Journal article did indeed show geocaching in area(s) that were illegal for the public to enter. He did not need to state which cache for his post to still be valid. Manager was not complaining about that cache. Manager indeed was not even complaining at all, about anything. Manager made one simple, extremely valid point: His concern over the fact that those that pursue geocaching in illegal areas can give the activity a reputation for causing probems, deserving of that reputation or not, especially when there are so many legal areas to pursue the activity. His point is valid even without knowing which cache initiated the comment. His point is valid even if he is not a land manager. His point is valid even if it was his first post. Manager did not complain about geocachers, about the cache, or about the activity. He voiced a concern. Yet, so many here saw fit to rip into him. I find that discouraging... To those that instead showed civility and politness, I thank you. _________________________________ Member:
  2. quote:Originally posted by Morty's Twisted World:I hid a magnet. Just a magnet. To some of us that have been at this awhile, we would classify that as geo-litter, rather than creative. Much like find the sneaker. _________________________________ Member:
  3. The event listing is HERE. and the WGA forums are HERE. _________________________________ Member:
  4. How about telling us what cache you are talking about. Just post its GC number or its ID number. _________________________________ Member:
  5. Bought one for the Mrs. last year, and I love it so much I stole it back We've given a few away as gifts. They are fantastic. Can't believe how quickly you can dial in or determine a bearing. _________________________________ Member:
  6. quote:Originally posted by Jamie Z:(I swear that I tried that before when I clicked on the "other search options" link and then the state, it sent me right back to the new state-search page in an endless loop. It did... I tried it last night in hopes of the original state search being available from the advanced search page, but it looped me back to the new state page. Now today I see it working the way I had hoped Jeremy, thanks for a great new state search page IN ADDITION to the original state search many of us love. THANKS!!! _________________________________ Member:
  7. quote:Originally posted by welch:id say yes, but more important is that theres no "good" way to search for a locationless. Considering that by definition, locationless caches have no location, I'm assuming that you don't mean you want to search by city, state, zip, country etc. That wouldn't make any sense. All that I can see that's left is to search by some kind of text, which you can already do. For example, if I click the 'Hide & Seek a cache' link, then type in 'historical marker' in the keyword search box, I get 7 caches that show up. Now agreed, by looking at the icon type I can't tell the true virtual caches from the locationless caches (which afterall is the whole point of this vote ), but by looking at the names I can get an idea of the virtuals. Like "Georgia Historical Markers" would probably be a locationless for the state of Georgia. So what kind of search are you looking for? _________________________________ Member:
  8. quote:I couldn't give two hoots if someone wants to log an event cache twice. It's their find count and there is no competition here. So if you find a cache at an event, knock yourself out. I gues my question is, what's the point? People at the event seek these things out, so what's wrong with using the event cache page? Jeremy Irish Thankyou Jeremy! I agree that there was probably mis-communication between us and Jeremy. Probably due to Jeremy entering the thread mid-stream and making his edict without catching up on the topic. The admins understood that I was referring to posting the find logs on the event page, and not submitting seperate individual caches. That's why I wanted to re-raise the situation on these forums, so that the issues could be re-discussed and perhaps reason prevail. As I said, I am very happy, and thanks all that pitched in here. Clan Ferguson, I'm personally sorry about your situation. My understanding is that the posting of very shortlived caches as their own stand-alone cache will not be accepted on the grounds of precedent setting and resources. Might I make a suggestion? How about making up your Halloween cache, getting it approved as a regular cache, and then just using the 'Temporarily disable this cache' feature to turn it on and off each year? Use the same cache page each year, making any updates to the page layout and contecnt that you desire. Just a thought. _________________________________ Member:
  9. quote:Originally posted by BrianSnat:What I think Jeremy is talking about is the creating of a page for each individual temporary cache to be placed during an event cache (picnic, etc...). What some others are talking about is placing several caches at an event and allowing people to log multiple finds for that event. I clearly explained to Jeremy and the admins that I was NOT talking about creating seperate individual pages for the temp caches, just to archive them a day later. I clearly said all we did was allow short, single line find logs to be made on the event cache's page that stated the name of the temp cache. Jeremy said no, that was not allowed. _________________________________ Member:
  10. quote:It seems to me that multiple caches at a single Event are atomic pieces of the complete Event. Yep, all part of the event. But they are still no less caches. quote:But you do the exact same thing with each stage of a multi, yes? You have coordinates, you go there, you hunt, you find a container. But that isn't logged in the multicache's log. Only the finding of the final cache allows you to log a Find on the cache. Are you talking about a multi-stage or a multi-cache? While each stage of a multi-stage must be followed to the final actual cache to count as a find is true, its not tru of a multi-cache where the cache owner has hidden one or more optional caches beyond the main one, and allows for finds to be logged for each of the optional that is found. I've seen many of these types of caches. quote:A single cache, yes. I don't know, has there been an instance of multiple caches being available after an Event? How have post-Event logs been handled in those cases? In the events I've been to, none of the temp caches were left active and available to hunt after the event was over. Post-event logging was all done on the event's page a short, single line find logs that state the name of each state the name of the temp cache that is being logged. _________________________________ Member:
  11. that this same topic is being discussed on two different threads at the same time. Don't miss the discourse on the other one that Clan Feruson has started. Jeremy is responding to that one: Other thread _________________________________ Member:
  12. Caches at events create no additional load whatsoever on the admins. quote:A multicache is a series of caches, but only one cache listing exists. An event cache can have multiple caches as well, but they shouldn't be listed separately. Agreed! As was explained in the discussion with the admins and yourself, the temp caches were not submitted as additional cache pages (with GC numbers), but rather were simply logged on the main event's page as short single line logs that state the name of the temp cache. Please see the 2002 WGA Geo-Picnic as an example. I too am against the practice of submitting one day caches for approval as individual GC records in your database. Its a waste of both admin time and database resources. That is not what was asked for, so many of us are still at a loss as to why they can't be logged on the event page. _________________________________ Member: [This message was edited by Team CacheCows of Wisconsin on October 15, 2002 at 02:59 PM.]
  13. How is hunting a physical cache at an event like a stage of a multi-cache? If I follow a set of co-ordinates with my GPSR, get to that spot and hunt around till I find the cache container, and am successful, then I found the cache. So why exactly am I only allowed to log that find if the cache is going to be around after the event is over. That is the ONLY difference. The permanence of the cache If the cache stays around after the event, then Jeremy says it can be logged. If it doesn't stay around after the event, it can't be logged. Tht's the determination. So how does that relate to your example? I don't see the analogy... Note that the difficulty of the cache has no bearing on if it can be logged. If its a 3 mile hike that includes rock climbing, but its at an event, then no find can be logged. However, if its 50 feet from a parking spot under a bush, but its permanent, then that one can be logged. I just don't get it. What exactly is the find count for? What's its purpose? We've all been told that its not a score. SInce its not weighted by terrain or hunt difficulty, it certainly doesn't measure a cacher's experiance level (cacher A has hunted 10 5/5 multi stages, cacher B has hunted 100 1/1 virtuals). So what use is the find count? Now we've learned that any caches we find at events aren't included in the count either, so now it won't even be an accurate count of how many we've hunted; for every event you attend and hunt caches, your 'find' count will start diverging from the number of caches you have actually found. I just don't get it... _________________________________ Member:
  14. James, WGA has been officially informed by Jeremy that caches must be permanent in nature for them to be logged. You will not find it in writting, but the admins will not approve caches that are not permanent. I don't know how it can be due to padding. Heck, the vast majority of temporary caches I've done at events are much harder finds than some non-event caches I've done. If I wanted to pad my finds, there are a couple of cities near me where I could hit a couple of dozen caches much easier than at events I've been to. _________________________________ Member:
  15. quote:Originally posted by Team CacheCows of Wisconsin: quote:Originally posted by CYBret:I've tried to see two Iridium Flares in the past couple of weeks, and both times I've gotten skunked. I was pretty close to the center on both of them, should I be looking overhead? How long do these things last? One other thing, when I signed up for the Heavens Above website, I entered my home timezone as US Central (Illinois). Everything else says I'm -6:00 from GMT, but Heavens Above says I'm -5:00. I'm wondering if this is the problem. Bret __"The kingdom of heaven is like treasure hidden in a field. When a man found it, he hid it again."_ Mt. 13:44_ Bret, 1) You must look at the _Azmiuth_ and _Alt._, not overhead (unless of course the _Alt._ coincidentally was _90°_. For the Azimuth, 0° is due north, 45° is NNE, 90° is east etc. around the compass. For the Alt., 0° is the horizon, 45° is hald way up the sky, and 90° is above your head. A rule of thumb is that the width of your hand held at arm's length is about 10°. They last about 3-5 seconds. Watch for the dim sat. as it approches the flare point, you will see the dim speck flare to intensity, then dim back to a speck. While were talking, I'll also mention that in the number displayed for the _Intensity_, the smaller the number the brighter, with a -3 being okay, and a -8 being great! Positive numbers (being bigger than negative numbers) are really poor. 2) Heavens Above automatically calibrates for daylight savings time, hence what looks like a descrepancy. _________________________________ Member:http://www.wi-geocaching.com _________________________________ Member:
  16. quote:Originally posted by Team CacheCows of Wisconsin: quote:Originally posted by CYBret:I've tried to see two Iridium Flares in the past couple of weeks, and both times I've gotten skunked. I was pretty close to the center on both of them, should I be looking overhead? How long do these things last? One other thing, when I signed up for the Heavens Above website, I entered my home timezone as US Central (Illinois). Everything else says I'm -6:00 from GMT, but Heavens Above says I'm -5:00. I'm wondering if this is the problem. Bret __"The kingdom of heaven is like treasure hidden in a field. When a man found it, he hid it again."_ Mt. 13:44_ Bret, 1) You must look at the _Azmiuth_ and _Alt._, not overhead (unless of course the _Alt._ coincidentally was _90°_. For the Azimuth, 0° is due north, 45° is NNE, 90° is east etc. around the compass. For the Alt., 0° is the horizon, 45° is hald way up the sky, and 90° is above your head. A rule of thumb is that the width of your hand held at arm's length is about 10°. They last about 3-5 seconds. Watch for the dim sat. as it approches the flare point, you will see the dim speck flare to intensity, then dim back to a speck. While were talking, I'll also mention that in the number displayed for the _Intensity_, the smaller the number the brighter, with a -3 being okay, and a -8 being great! Positive numbers (being bigger than negative numbers) are really poor. 2) Heavens Above automatically calibrates for daylight savings time, hence what looks like a descrepancy. _________________________________ Member:http://www.wi-geocaching.com _________________________________ Member:
  17. quote:Originally posted by CYBret:I've tried to see two Iridium Flares in the past couple of weeks, and both times I've gotten skunked. I was pretty close to the center on both of them, should I be looking overhead? How long do these things last? One other thing, when I signed up for the Heavens Above website, I entered my home timezone as US Central (Illinois). Everything else says I'm -6:00 from GMT, but Heavens Above says I'm -5:00. I'm wondering if this is the problem. Bret __"The kingdom of heaven is like treasure hidden in a field. When a man found it, he hid it again."_ Mt. 13:44_ Bret, 1) You must look at the Azmiuth and Alt., not overhead (unless of course the Alt. coincidentally was 90°. For the Azimuth, 0° is due north, 45° is NNE, 90° is east etc. around the compass. For the Alt., 0° is the horizon, 45° is hald way up the sky, and 90° is above your head. A rule of thumb is that the width of your hand held at arm's length is about 10°. While were talkking, I'll also mention that in the number displayed for the Intensity, the smaller the number the brighter, with a -3 being okay, and a -8 being great! Positive numbers (being bigger than negative numbers) are really poor. 2) Heavens Above automatically calibrates for daylight savings time, hence what looks like a descrepancy. _________________________________ Member:
  18. quote:Originally posted by CYBret:I've tried to see two Iridium Flares in the past couple of weeks, and both times I've gotten skunked. I was pretty close to the center on both of them, should I be looking overhead? How long do these things last? One other thing, when I signed up for the Heavens Above website, I entered my home timezone as US Central (Illinois). Everything else says I'm -6:00 from GMT, but Heavens Above says I'm -5:00. I'm wondering if this is the problem. Bret __"The kingdom of heaven is like treasure hidden in a field. When a man found it, he hid it again."_ Mt. 13:44_ Bret, 1) You must look at the Azmiuth and Alt., not overhead (unless of course the Alt. coincidentally was 90°. For the Azimuth, 0° is due north, 45° is NNE, 90° is east etc. around the compass. For the Alt., 0° is the horizon, 45° is hald way up the sky, and 90° is above your head. A rule of thumb is that the width of your hand held at arm's length is about 10°. While were talkking, I'll also mention that in the number displayed for the Intensity, the smaller the number the brighter, with a -3 being okay, and a -8 being great! Positive numbers (being bigger than negative numbers) are really poor. 2) Heavens Above automatically calibrates for daylight savings time, hence what looks like a descrepancy. _________________________________ Member:
  19. I also discovered this morning that many of my cache pages had broken images. In the old days Jeremy kept uploaded images at http://www.geocaching.com/cache/images/ but later moved them to http://img.Groundspeak.com/cache/ If you had a graphic on a cache page that linked to an image stored on another cache page as you have in your example (I also have many of these) that used the old location instead of the new image server, they still used to work up until yesterday's static page change. To fix the problem, all you have to do is go edit your cache page and change the img tag to the new location. Fortunatly the name of the actual file at the end of the tag (i.e. 10321_1800.jpg) didn't change, only the server address. In all honesty, we've been on borrowed time for a number of months. We really should have updated these links when Jeremy first put the image server online. Happy Caching! _________________________________ Member:
  20. I also discovered this morning that many of my cache pages had broken images. In the old days Jeremy kept uploaded images at http://www.geocaching.com/cache/images/ but later moved them to http://img.Groundspeak.com/cache/ If you had a graphic on a cache page that linked to an image stored on another cache page as you have in your example (I also have many of these) that used the old location instead of the new image server, they still used to work up until yesterday's static page change. To fix the problem, all you have to do is go edit your cache page and change the img tag to the new location. Fortunatly the name of the actual file at the end of the tag (i.e. 10321_1800.jpg) didn't change, only the server address. In all honesty, we've been on borrowed time for a number of months. We really should have updated these links when Jeremy first put the image server online. Happy Caching! _________________________________ Member:
  21. When you type the URL into your log entry, just make sure you put a space at the end of it and it will work fine. That way the " [last" won't get fastened to the link. _________________________________ Member:
  22. Miss it? Sure... but IMHO the loss of the finds stats is nothing compared to the performace we've gained by Jeremy making the cache pages static, which is what necessitated the loss of the finds counter. Thanks Jeremy! _________________________________ Member:
  23. Miss it? Sure... but IMHO the loss of the finds stats is nothing compared to the performace we've gained by Jeremy making the cache pages static, which is what necessitated the loss of the finds counter. Thanks Jeremy! _________________________________ Member:
  24. -Alan, Arlene, Eryn _________________________________ Member:
  25. Artful, Where the object tag fails is when you try and use it for increasing the amount of allowed text and or images. It fails for three reasons: The height and width of the object have to be stated, and there is no way of knowing what the length of the object will be since you can't control the size that the viewer's browser is displaying the text size in. If you screw up the height or width, then scroll bars appear around the object (looks bad and the stuff outside of the scroll area won't print) printing results are spotty at best. Often the results are misaligned with left or right sides missing Display results vary depending on browser. The way you are using the object tag in your example is indeed an excellent use as most of the content is not displayed. The only thing displayed is the graphic, and you can know and control its height and width. But if the goal is to add additional text, the object tag does not cut it. Fortunatly, its all mote now that Jeremy increased the allowed description. _________________________________ Member:
×
×
  • Create New...