Jump to content

Setan Meyacha

+Premium Members
  • Posts

    96
  • Joined

  • Last visited

Posts posted by Setan Meyacha

  1. To hide a micro, using a little ingenuity, a $1. or less investment.

    A good point. Something else I've noticed is that those folks who spew out micros everywhere they can, seem to favor those containers which experience has shown to be less able to protect their contents. While I do find the occasional crappy regular and small, by far, the majority of the crappy containers I've seen have been micros, either black & grey film cans, hide-a-keys and/or Altoids tins, none of which are suitable for any environment with more than an average 0.01% humidity. A good rule of thumb I like to babble: If your container requires a ziplock to protect its log, your cache has already failed at a very basic level. With match safes costing $0.88, and preforms costing about $0.60, (both having excellent track records in all environments), I can't see any reason folks would intentionally select a crappy container to present to the world, unless they simply don't care. By taking pride in our hides, regardless of size, soggy logs could mostly become a thing of the past. :)

    Actually, I think you missed the point all together. I'm sure there are some who just put a micro somewhere just because it can be placed there. That wasn't the point. The point being, because of the higher cost of placing ammo cans, people on restricted budgets find it easier to 'stay in the game', by placing micro caches over ammo cans or even small caches with trinkets in them. I use used diabetic strip containers; no worry about wet logs unless some idiot doesn't close the lid after signing the log. Not much control over that. As some of my earlier containers (not the type I'm using now) require 'first aid', I replace them with the containers I use now. And I do still hide an occasional ammo can and quite a few small containers; most not containing dollar store junk. I guess the question is: if I lived in your area would you prefer I only hide one or two caches a year (ammo cans), or quite a few more using micro caches in quality places?

    That question wasn't for the 'micro haters'...the ones who ignore all micros!

  2. I think one thing some people fail to realize is the affordability factor determining the size and amount of caches a person hides. To place an ammo can-sized cache, stocked properly, is a $20 - $25 investment. To hide a small container, assuming it will hold more than just a few tiny trinkets, is a $5 - up investment. To hide a micro, using a little ingenuity, a $1. or less investment. Unless you're hiding in-town caches close to home there is the added expense of travel to find a hiding place.

    For those on SS or other limited income, the choice in container size becomes obvious on a budget already stretched thin.

    I do hide some 'lame' guardrail, just beside the road, and other 'lame' location caches that are easily found by those less fortunate who can't get into the 'outback' to search for caches. But, the majority of my caches, micro, small and ammo can, are hidden in more scenic and more difficult places to reach. I get as much enjoyment in hiding caches as I do in finding them, unless they are located in country settings or places of scenic interest.

    Guess you could say I'm a fan of the micro; whether hiding them, or finding them.

  3. I pick a lot of my cache hiding places using GoogleEarth; but, only as a general location until I actually get to the spot to find out whether it is worth placing a cache in that location. Then, after I've found a hiding spot, I use my GPSr to take a number of readings to be as accurate as I can be in the coordinates posted. Sometimes rock walls, water, trees or other factors can still put those coordinates off by as much as forty feet, in one instance. When that happens, as usually the FTF will let me know, I go back out and see if I can find the same location using my original coordinates. If not, then I adjust the coordinates based on what the finder thought they should be and an average of the new coordinates I take at that time. I've only had one cache placed almost exactly in the spot I picked out on the map. I only use GoogleEarth as a means of finding likely hiding spots.

  4. I've hidden caches under two different names. Under my current name I have one cache that has yet to be found and it was hidden on 6-18-08 and is an ammo can. I have 10 others that haven't been found in over 1 year. Under my other name I have six caches that have yet to be found, 44 that haven't been found in over a year, and 10 that haven't been found in over two years. Of course, all of those caches are hidden in desert/canyon land country and most require a bit of hiking to reach them. Most of my caches get very few visits outside of the local cachers because you don't have an opportunity to rack up the numbers by chasing after most of my caches. And I've found that people from outside the area are a little hesitant to venture into some of the areas where I've placed my caches. Does keep the maintenance problem to a minimum though, and that's not all bad. The ones who have found those caches seemed to have enjoyed where the caches took them.

  5. "I comment in the forums using my personal account. We have a team account for our hides. We've been hiding since 2002. 36 hides. All caches have swag which we replenish a couple of times a year. No log-only caches. No film canister caches. Most are lock n locks. One is an ammo can. All maintained in a timely fashion."

     

    I'm glad to hear your team has hidden 36 caches in the past 8 years. I would imagine if I were part of a team instead of placing all my caches on my own, there would be more caches that were larger than micros, but only those I would have hidden as part of the team. I would still hide the micros. And I can assure you, when I do hide the larger caches they do contain more quality items than I have ever found in similar sized caches.

     

    One of the great things about this sport/hobby is that you can pick and choose which caches you want to go after; if you don't like micros, don't go after them.

     

    "I have been forced to filter out micros. Unfortunately that means I miss out on the 2% of micro hides that are placed with imagination/ingenuity/cleverness but so be it. Many micros get listed as small - that irks me, especially when I suspect they were listed that way to avoid the micro filterers.

     

    I am kind of curious how you came up with the 2% of micro caches that are placed with 'imagination, ingenuity, and cleverness? Haven't seen those figures proposed anywhere else, yet. Not sure why someone would list a micro as a small unless they might be new and don't know the difference. I doubt seriously it would be done to avoid the micro filters. Who really cares if someone avoids your cache because it is a micro? I certainly don't or I wouldn't be hiding them.

     

    You can look up my profile(s) under greywolf1242 as well as Setan Meyacha.

     

    Something the 'micro haters' apparently don't take into consideration is the time, expense and locations some of these micros will take you to.

     

    "What expense? My experience is that people hide film canisters because they cost $0. The CO doesn't even supply a cut down pencil, the paper is usually scrap paper. So there's is no expense to the CO. In terms of time, it surely takes less time to hide a micro, as they will fit in far more places then a regular size cache. It takes more time to look for a good hiding spot for a larger cache."

     

    I have hidden very few film canisters. My micros come in all forms, but mostly the empty containers from my diabetic test strips. As far as expense: unless gas has dropped to near zero in your neck of the woods, it is 2.73 a gal around here, higher if not bought locally. None of my logs are scrap paper, although I have seen scrap paper used in ammo can-sized caches also. I've hidden both large and micro caches and they both take about the same amount of time; actually, sometimes the micro can take longer to find just the right spot that will afford the seeker a good opportunity of finding the cache.

     

    "Sure some of those micros are planted in with care, investment and imagination but 98% of micros aren't planted that way. I'm not going to get to visit the good ones because I've been told... don't like lame micros then filter all micros out."

     

    Unfortunately, I've come across just as many non-micro caches that were 'lame', as micro caches that are 'lame'. Not every cache I go after is going to be a 'high-quality' cache and I realize that before ever heading out the door. I guess it depends on your purpose for seeking out a cache.

     

    If you plant micros that are planted because you want to bring people to a nice location that won't support a larger cache, or you hide creative micros that make a finder smile, or laugh, or think "Wow" or "Cool" or "Clever" then good on ya. That's commendable. Keep up the good work.

     

    I'm sure that the majority of my caches, whether micro or ammo can, would hardly meet your high standards of what a cache should be. Perhaps after a few more years, assuming I live that long, I'll adopt the same attitude.

     

    BTW, you can look up my profile(s) under greywolf1242 as well as Setan Meyacha. I take the credit, as well as the blame, for all caches placed under those names.

  6. "My pet peeve - COs that don't invest in the game. They play the game for a week, maybe a month, find no caches or a couple of caches then put out micro caches that cost $0 to create. Promptly get bored and disappear, leaving it up to the community and the reviewer to finally do the archiving."

     

    I don't know that I would call it a 'pet peeve', since I normally think of stroking and petting a pet, but I have noticed that some of the people who complain the most about micro caches are those who have yet to contribute any or very many caches of their own to the sport/hobby. And I would be more than happy to take all the $0 cost micros anyone would like to send my way.

    One of the great things about this sport/hobby is that you can pick and choose which caches you want to go after; if you don't like micros, don't go after them. If you know a particular CO hides primarily micros and doesn't list the type of cache container in his/her description...just don't go after those caches; holdout for the ones you know will have lots of 'goodies' you can trade for or, at least, make your search easier.

    Something the 'micro haters' apparently don't take into consideration is the time, expense and locations some of these micros will take you to.

    I am a MICRO hider!!! And I hide them in hard to find places; so, you'll want to avoid the majority of my caches. Although I do hide small to large caches also, and have hidden caches under two names, most of the caches I've hidden are micro caches. Have only received a couple of complaints by e-mail about them, but plenty of positive e-mails and logs about some of the places my 'micros' have taken them.

    If someone wants to supply me with ammo cans, I'll be happy to hide them, once in awhile. But, I'll still stick to the micro as my primary cache container.

  7. I think these power trails are appalling. Groundspeak is going in a bad direction by allowing this.

     

    I agree. It is worrisome. I wonder what made Groundspeak change its' collective mind about the issue of power trails. Do power trails bring in more revenue?

     

    Imagine having to ignore all of these caches, one at a time? Now that Groundspeak allows PTs, perhaps they can also provide a feature which allows ignoring all caches by a CO, en masse.

     

    Are ignore lists limitless or is the list full at 500 caches?

     

    I guess I find it difficult to find what is so 'appalling' about someone taking the time, energy, and expense to lay out a 'power trail' for other people's enjoyment in finding those caches. And I also find it difficult to understand why anyone would want to 'ignore all caches by a CO, en masse', unless it was a known fact that the CO placed caches in hazardous places or on private property without permission. If all a person is interested in is finding a cache loaded with goodies to trade for and not the experience of finding the cache in a possible location they have never visited before, then ignoring all caches by a CO might be the way to go.

    I hide most of my caches in the country and most of those are in the desert. The majority of places where I hide caches are rarely visited by other cachers for the purpose of hiding caches. So, it is easy for me to be accused of 'over-saturating' an area with caches by being just about the only one hiding caches in those areas. Rarely are any of my caches closer than .2 miles from another cache.

    There is an area of desert approximately 30 x 23 miles not far from where I live that I plan on placing quite a number of caches throughout the summer. There are probably not more than 20 caches in the area in question, and most of those are close to US Hwy 75 and Hwy 20. If my placing those caches results in someone(s) 'ignoring all my caches, en masse', that is fine with me...it is your loss.

  8. I am still learning to use my gps i have a GARMIN etrex vista i had it now a few weeks and every other morning when i am satting in the market cafe eating breskfast and drinking coffee and mess with it and i found thta it has a battery bar letting me know h0w much power that i have left that is a A-plus for me to know the power i have left,and also i did notice that upon turning it on this unit belongs to ///it shows blank how do i get my name on it or in it??/

    That is one looooong sentence!!!

  9. The areas I like to cache in the most are probably the most likely to have a major accident in; desert, canyons and mountains of Southern Idaho. But, I’ve either been very lucky or have an angel on my shoulder….except on one caching trip with a very good friend of mine. We were nearing the end of the day of caching and still about 50 – 60 miles from home, when we came to a cache that only took us about 3 minutes to walk to from where we parked his Jeep. It was a wooded area not far from Anderson Ranch Reservoir with a trickling stream running near the cache site. We had to bushwhack to get to the cache site and since I was in the lead it was only natural for me to attempt to get either up and over the huge boulder where the cache was hidden, or fight my way through the thick brush surrounding the boulder. I chose the first option.

    The boulder was covered with wet moss and numerous twigs and branches from the trees overhead. It slanted on a fairly steep angle and as I neared the top of the boulder I stepped on a wet limb and my foot went out from under me. I came down on the sharp edge of the boulder about four inches above my ankle on my shin bone. Fortunately, there was a tree limb to keep my forward momentum from propelling me over the edge of the boulder.

    After rocking back and forth clutching my shin bone with both hands for several minutes, I convinced my friend I was okay enough to continue the pursuit of the cache. It was found, I signed the log for both of us so he wouldn’t have to make the same journey, then found an easier way around the base of the boulder back to the ‘trail’.

    It took us (me) nearly a half-hour to make it back to the Jeep and another five minutes trying to figure out how to get my leg in the Jeep without causing any further pain. My friend did the remaining few caches on our way home and I found out, much later, that I had a splinter fracture of my shin bone and chipped a piece of bone off that still gives me fits if I bump my leg the wrong way 3 years later. I was a gimp for a couple of months that probably could have been shortened if I would have just had it checked out sooner.

    No bee, wasp or hornet stings…to date. No stinging nettles, no poison oak or ivy. Close, but no snake bites…just tons of fun exploring the world around me.

  10. I’m not a big fan of city caches, so most of my caching (both hiding and seeking) is done in the desert, canyon lands and mountains of Southern Idaho. Quite obviously, spending very much time in those settings is bound to increase a person’s chances of having ‘close encounters’ with wild critters. I’ve had the pleasure of seeing numerous deer, elk, antelope, coyotes, and other four-legged creatures both large and small; sometimes, when I’ve been lucky, a very close quarters.

    Unfortunately, your chances of encountering the not so pleasant critters is just as great. I’ve had very close encounters with rattlesnakes of all sizes. The picture I’ve added is of just one such encounter. While searching for a benchmark I stepped within inches of this rattlesnake as it was headed ‘somewhere’ and was in a hurry to get there, fortunately. It picked the closest hiding spot, which didn’t go deep enough for the snake to really hide, affording me the opportunity to get a couple of pics after my pulse settled back down.

    One other encounter with a ‘huge’ rattlesnake came just after hiding a cache near a spring in the desert north of the Gooding City of Rocks. I was on my way back to my van when I nearly stepped on a rattlesnake estimated to be about 6 feet long. Part of the snake was in the brush and the rest on the game trail I was walking on. I don’t think any 64 year old man could have one-foot hopped as far as I did to avoid stepping on that snake. I think I covered ten feet in that one-footed hop. After my heartbeat got back to normal, some minutes later, I thought about trying to get a picture of the snake; but, common sense won out and I went on down the road to hide another cache.

    100_4075.jpg

  11. I have an idea, albeit probably not new. B) What do you guys think about this:

     

    Let's start allowing finders (not DNFs...finders only) to vote on cache ratings. It wouldn't be a requirement, but optional. They could rate the cache as they see fit.

    SNIP

     

    I think this is an excellent idea. I've been to some rather overrated caches, and having a chance to see some user ratings might help eliminate wasting time on a cache rated 4 stars for terrain, because there was a slight hill.

     

    I have also seen caches rated fairly low that took people multiple trips and much time searching to find. These jewels should be allowed to shine forth, too.

     

    How about two sets of ratings: the ones the CO comes up with, and an average score from all the finders.

    I'll admit that some of my caches are probably 'over-rated' to someone in their prime or younger for Terrain difficulty. However, the majority of cachers who have logged most of those caches are in the over 55 age bracket and I haven't heard any comments about the ratings.

    If there were a way for a person to rate the cache and have running averages shown on the cache page, as opposed to being mentioned in the log only, that might give some people more incentive to go after the more 'difficult' caches that don't truly rate a higher difficulty rating for the younger crowd. It would also let the 'over 55' crowd know that it isn't a walk in the park.

    Doubt it will ever happen though.

  12. I posted the following on the GSAK forum, but there doesn't seem to be a whole lot of activity over there and I need an answer asap. If anyone can help with this it would be much appreciated. I've already put over 300 waypoints in GSAK-one at a time- and would like to prevent losing them if at all possible. I don't think a simple reinstall is going to fix the problem.

    From GSAK forum:

    I installed GSAK, version: 7.6.2.45, yesterday and everything seemed to be working fine. This morning when I tried to start GSAK, I got the following 'EAcess Violation' message:

    2.1 Date : Mon, 1 Feb 2010 08:26:23 -0700

    2.2 Address : 009ACC00

    2.3 Module Name : gsak.exe - (GSAK Geocaching program)

    2.4 Module Version: 7.6.2.45

    2.5 Type : EAccessViolation

    2.6 Message : Access violation at address 009ACC00 in module 'gsak.exe'. Read of address 00000000.

    2.7 ID : 06B2

    2.8 Count : 1

    2.9 Status : New

    2.10 Note :

    I am running Windows Vista Home Premium.

    The only way I can get out of the GSAK startup is to end it through Windows Task Manager.

    What is the problem and how can I correct it?

  13. Um...At the risk of having you think I'm one of "those" responders I gotta ask. You do realize that 15-20 feet is well within the margin of error of consumer grade GPS receivers, right?

     

    I don't know whose receivers are always at 15 to 20 ft, but my Garmin Rinos are ALWAYS within 6 to 8 ft?

    Huuum? I have a Garmin GPSmap 60C and do most of my caching in the deserts of Idaho. Even on a good day it is not unusual to get a reading that is only 15' accuracy; that, btw, on caches I'm looking for. When I place a cache I'll take as many as 5 or 6 readings if they aren't consistent, due to rock formations, large bodies of water, trees, etc. If I have clear skies and unobstructed views, my unit rarely shows a difference of more than .001 between all the readings I take. That doesn't mean the person looking for my cache is going to have the same degree of accuracy. I think the "ALWAYS within 6 to 8 ft" might be just a little bit of a stretch.

  14. I'm guilty of the 'cut and paste' type of logging. However, in most cases it is just the first part of the log that is 'cut and pasted' into the log; i.e. 1st of 42 caches on my trip to.... The rest of my log will usually have something to say about that particular cache or something that happened in finding it.

    On the receiving end: I have a number of caches hidden over a wide area; some, I must admit, are basic 'park and grab' type caches, but others are what I consider quality caches if for no other reason than the area they take you to. When I see a 'TNLNSL TFTC' posted on these 'better' caches it does kind of irk me that the person finding the cache didn't appreciate the time, effort and expense involved in placing the cache to say something about their experience, good or bad.

    When I get well-thought out logs posted I will usually send an e-mail to the poster to thank them for their comments and express my appreciation for them taking the time to search for my caches. Hopefully, this will induce them to keep making similar posts on other caches, if they haven't already adopted the attitude that any cache placed has taken some time, effort and expense to place it; making it worthy of even a short comment, rather than the 'cut and paste' TNLNSL TFTC.

  15. Unless the cache location poses imminent danger to a cache seeker, the issue should be taken up with the CO first. But, keep in mind that we all have the choice to make in pursuing a cache that appears to be in a dangerous location.

    One of my first few caches violated one of the rules of placing caches and the reviewer not only notified me of the violation but also offered up an acceptable solution so I could keep the location as part of a multi-cache that has been fairly popular. I think, in most cases, the reviewers are quick to notice when a cache may be in violation of one of the 'rules'. In those cases where they might miss one because they are unaware of property issues, it is still best to contact the CO first and express your concerns in a 'tone' that you would use in a face-to-face meeting. I am not, by any stretch, an authority on all the rules and would hope not to come across that I am in offering up a suggestion or concern to a CO who MAY have violated one of the rules of cache placement.

  16. I, personally, avoid caching at night within city limits. I do cache at night in the desert though, and the only thing to really be concerned about there are the creepy crawlies. I've hunted coyotes for years, so don't concern myself with them; especially when caching at night in the desert you most likely are, or should be, carrying a flashlight and/or wearing a headlamp to see where you're going. Nighttime caching in the desert in the summer is the best way to cache...less heat!

  17. I have too many caches out to be checking on them unless they need attention. I did have one cache that no one found for quite some time and there were a number of DNFs logged. The day before I was going to travel the 30+ miles (round trip) to check on the cache someone finally found it. I have had to make a 40+ miles (one-way) trip to check on a cache when it was reported missing only to find someone put it where they 'thought' it should be and not where it was found.

    Now, if one of my caches is reported as missing, I'll see if any blue faces show up before going to check on it, unless it is nearby.

    However, a good many of my caches probably don't see more than a dozen or so logs in a year's time; so not a lot of need for maintenance.

  18.  

    I would not hesitate to place a hide on my land, if I had more of it. We need more hides. My guideline would be: Would I let MY kids run wild in the area? If the answer is no, then I would not place a hide there.

    A lot of land is not necessary if you want to place a cache on your property. I live in town, unfortunately :) , but I have a cache located in the front yard. And, yes, it is stipulated in the description that it is on private property with permission. It is a good way to meet other cachers that you might not otherwise meet through your local Meet & Greet functions. I've met several out-of-state cachers I would not otherwise have met. And you can be very creative in the type and placement of your cache even in a postage stamp-sized yard. I would agree with other posts that you might want to find several types of caches before placing one of your own just so you can see how others have done it. Perhaps you'll find one you can improve upon for your own situation.

    Anyhow, welcome to the sport/hobby/addiction and good luck!

  19. Placing Caches on Public Lands

     

    How many of us have been guilty of placing a cache somewhere without asking permission just because another cache or caches have been placed in the area; namely city, county, state parks or other public lands? I know I’ve been guilty of this on more than one occasion when I saw there was another cache or two placed within the given area I planned on placing a cache. I wrongfully, most likely, assumed that the previous cache placers had already received permission…giving me, by proxy, the same permission; which isn’t necessarily the case.

    I know it can be a hassle tracking down the proper people to get permission from to place a cache. Sometimes it takes repeated phone calls or e-mails, if you know their e-mail address, to get a response. And, in most cases, we already have an idea of where we want to place the cache and what type. But, if you are like me (a little impatient and eager to place the cache), we just go ahead and do it and hope for the best. Sometimes the reviewer will catch a submitted cache as being where it shouldn’t be and we get it denied; usually, in most cases, because we forgot some of the rules of placing caches.

    The Bureau of Land Management, as a rule, doesn’t have any stipulations about placing caches in areas they manage; with the exception of Wilderness Study Areas. Although they don’t deny, at the present in Idaho, the placement of caches in a Wilderness Study Area, they do monitor caches placed in such areas to determine if they are detrimental to the environment in which they have been placed. In most cases, the most you would have to do is move the cache sufficiently to prevent ‘trails’ being made to the cache.

    But, back to the subject of city, county and state parks. I was glancing through some of the posts on geocachingcolo.com when I came across a link to the following from the Colorado Springs, CO Parks, Recreation & Cultural Services Dept.

    “GEOCACHING GUILDELINES FOR CITY PARKS & OPEN SPACE AREAS

    COLORADO SPRINGS, COLORADO

    In response to the growing sport of geocaching, the City of Colorado Springs Parks, Recreation & Cultural Services Department has implemented a set of guidelines that works to allow certain activities and/or caches, and at the same time limits the risk of unattended, closed containers being left in the park system. The two main concerns of the Parks Department are: 1) The traditional cache, or large physical container associated with geocaching, and; 2) any activity that promotes off-trail hiking.

    Traditional caches: Traditional caches (ammo cans, Tupperware containers, boxes, etc.) are not permitted in any park or open space within the jurisdiction of the City of Colorado Springs. If a traditional cache is discovered, the team responsible for placing the cache will be contacted via email, along with a letter and copy of the geocache guidelines. Teams will then have a two week period to remove the cache. If the cache is not removed within two weeks, Parks Staff will dispose of the cache.

    Micro caches: Certain micro caches are permitted in parks and open spaces within the jurisdiction of the City of Colorado Springs. The micro caches allowed include any clear plastic ID card holders (wallet-sized) and small containers basically the size of chap-stick tubes. Micro caches must be placed on or directly adjacent to a designated trail.

    Virtual caches: Virtual caches are permitted in parks and open spaces within the jurisdiction of the City of Colorado Springs. Please post the coordinates for a virtual cache on a designated trail. (Palmer Park & Ute Valley Park offer great rock formations and views for virtual caches.)

    Tags and post-its: Tags are permitted in parks and open spaces within the jurisdiction of the City of Colorado Springs. Tags are most common in association with multi-caches, and are simply laminated or metal tags with coordinates, clues or other text listed on them. As with micro or virtual caches, please locate the tag on a designated trail. (Existing trail signage is a good place to post these, as long as the tag does not damage or obscure the sign.) Tying the tag to a tree with string, wire or plastic is OK, as long as the tree is not damaged in the process. Nailing, stapling, or tacking tags to trees is prohibited.

    Geocache events: If a team wishes to host a one-day event, geocaches will be permitted (including traditional caches), as long as the caches are placed on designated trails the same day as the event, and are picked up immediately after the event. The containers should be clearly marked with the date and name of the team and/or event. The hosting team must supervise the event in a manner that minimizes the chance an outside group or person might tamper with the caches throughout the event.

    Parks Staff will continue to monitor any new caches. New caches that conform to the above guidelines do not require prior approval from Parks Staff. If you or your team has questions, please contact the Parks, Recreation & Cultural Services Department at 385-5940 or email CityParks@springsgov.com.”

    As you can see from these ‘guidelines’, they are fairly restrictive and may be just a hint of what could happen in your given area if there isn’t more interaction between the land managers and the geocachers desiring to place caches in such areas. We all have read the rules about placing caches and know that prior permission to place a cache is ‘supposed’ to have been obtained. But, you and I know that hasn’t always been done. And short of even more restrictive ‘rules’ having to be made by geocaching.com to ensure that permission has been granted, it behooves us to impose stricter ‘rules’ upon ourselves to insure our sport continues to grow and prosper. It would be a shame to visit a large park, (city, county, state or otherwise) knowing the largest cache we can search for is a micro.

    Do your part…seek permission before placing a cache! And periodically check back with the land manager to make sure new ‘rules’ haven’t been implemented that would preclude you from placing additional caches in the same park or other public lands areas.

  20. I'm currently working with the BLM and Idaho Fish & Game in planning a few CITO events for this summer. This will be my first event(s) and I've been unable to find any information on whether it is kosher or not to place several caches in the event area prior to the event as an inducement to get more participation. Of course, the caches would not be listed until the day of the event so those participating would have first opportunity for FTFs. Can anyone tell me if there is some rule concerning this subject and where I can find it? I've searched high and low for a contact number so I could explain in greater detail what I'm planning, but I can't find one anywhere. Perhaps someone could help me with this problem also?

     

    Thanks,

    Setan Meyacha

×
×
  • Create New...