Poison Ivy has surrounded my cache...

[+hammerstriker]

So I've noticed that my cache has become surrounded by poison ivy... should I relocate the cache, or just let the seeker beware?

 

Thoughts / opinions welcomed!

 

HammerStriker

[+BBWolf+3Pigs]

So I've noticed that my cache has become surrounded by poison ivy... should I relocate the cache, or just let the seeker beware?

 

Thoughts / opinions welcomed!

 

HammerStriker

 

If it can be moved slightly to avoid it, I would try to do that. Be sure to update the coordinates as well as the hint (if applicable). In the mean time, use the Poison Plant attritbute, and maybe even add a note in the cache listing.

[+TXHooligans]

here, it's generally frowned upon to poison, burn, destory, etc anything growing in nature.. unless you eat it.

 

at my house it gets destroied by any means.. if it's your property it's your choice.

 

i'd note it in the description as well as note it with the attributes if it can't be easily moved.

[+Semper Questio]

If the PI can be avoided, I'd add the attribute and make an appropriate comment in the description. If not, I'd move it if I could or archive it. Having been a serious victim of that wicked little plant, I won't subject others to it.

[+mpilchfamily]

That's what the attribute is for. PI tends to grow out all over the place so you would probably have to move it a ways away.

[+briansnat]

If people can reach it without touching the plant if they are careful, I'd leave it and put the attribute on the page and probably warn about it in the cache page text.

 

If there was no way of reaching it without contacting the plant I'd probably move it.

[+StarBrand]

If people can reach it without touching the plant if they are careful, I'd leave it and put the attribute on the page and probably warn about it in the cache page text.

 

If there was no way of reaching it without contacting the plant I'd probably move it.

Agreed. A slight move of 20 to 30 foot should be no big deal in most cases (if you update the coords) - but only do it if absolutely necessary.

[+the4dirtydogs]

If the cache was mine I would move it. Im highly alergic to the stuff. Thats why I keep alcohol wipes with me when hiking. I've had to move a couple caches due to this plant. I still manage to get the itch a couple times a year

[+Sol seaker]

I would definitely move it.

 

The problem with a poison oak allergy is that one can go for years without any reaction, and then suddenly get a really huge reaction.

I would not take the chance with others safety and health.

 

AND not everyone reads the cache pages or the attributes. I'd hate to find out someone showed up with a small child that was hospitalized because of it. A child will run ahead to find the cache and won't know what it looks like. They can be covered in it before the adult gets near.

[+hzoi]

Change the question a little, and I would argue that this question answers itself.

 

Examples:

-Rusty thumbtacks have surrounded my cache.

-Broken glass has surrounded my cache.

-Nests of angry hornets have surrounded my cache.

-Bags of smelly garbage have surrounded my cache.

 

Put another way: would you want to go hunting for it now? (And do you really want to make maintenance trips to it now?)

[+Bad_Wolfe]

I say leave it. No Rash, No Cache!

[+geodarts]

For a long time, I did not have any reaction to poison oak (which grows in my area), but after a couple of minor bouts I decided I needed to be more careful and at least use technu after going into some of the places that I end up searching. So I have found caches hidden directly in the plants, generally where the CO did not know how to recognize it or the cache is old enough so that the area has been overrun. And some cache owners have no problems in placing hides in the middle of old growth areas, under tree cover where the gps reception is sketchy -- and I figure that I can always make up my mind about whether to search or not.

 

However, when my caches have been overrun with it over time, I have moved or archived them. I have no interest in making that part of the search and saw no reason to bring cachers to that particular spot when other places would do as well. If I do not have a good reason when I ask myself "why" I will go on the side of caution.

 

Still, I have caches where there are plants in the area, along the sides of the trail and into the brush. I have advised cachers on the page that the poison oak is not part of the search, that they should be careful, but there is no need to look among poisonous plants.

Edited March 2, 2011 by mulvaney

[+EscapeFromFlatland]

So I've noticed that my cache has become surrounded by poison ivy... should I relocate the cache, or just let the seeker beware?

 

Thoughts / opinions welcomed!

 

HammerStriker

 

[+knabino]

If you do nothing else, put in big letters at the top of your cache description that there is PI in the area. There are some who are HIGHLY allergic to the stuff no matter what preventive solutions they use. Its nice to know at the start that there is PI in the area.

[Luckless]

I would definitely move the cache. I want people to have fun looking for my caches and getting a dandy case of poison ivy doesn't fit that senario.

Are you sure it's poison ivy? I had a couple of people who were visiting from 500 miles away do my four stage multi puzzle cache only to get mad at me because as they said there was poison ivy growing all over the place where the cache was hidden and they didn't want to get into it to find it. They were really upset to have spent all that time looking and then not be able to get to the cache. Well there was a three leaf vine growing all over, but it wan't poison ivy- some kind of creeper. I picked leaves from anything that looked like poison ivy and took them to a botany specialist, but by then the cachers were having nothing more to do with my cache. Oh well.

Edited March 2, 2011 by Luckless

[RainbowKat]

For the love of all that is good and not itchy, please move it!

 

Did you know you can get poison ivy from another person? I don't want to shake hands with a geocacher who's just touched your cache!

[+ocklawahaboy]

The answer to your question lies in whether you want this to be a dangerous cache or not. I've gotten PI so bad when looking for a cache that I had to go to the doctor and get some good ol drugs to get over it. I don't hold that against the CO because that's just part of being in the area where the cache was. I looked at it no differently than if I'd made a mistake navigating any of the other hazards that go along with certain caches.

So, if you want a benign cache, which is fine, move it.

If you want a more challenging and potentially dangerous cache, leave it and warn the cachers of the danger.

[Wallydraigle]

Up the difficulty and just let the situation work itself out?

[+simpjkee]

I'd probably move it, but just updating the cache page with the attribute and warning is easily sufficient.

 

I would not kill the plant. Thats lame that anyone would recomend that.

[+John in Valley Forge]

 

No mercy on PI. Kill it off and move the cache away a little bit.

Maybe wipe the cache container down with rubbing alcohol.

[+Lil Devil]

+1 on the chemicals. Kill that stuff dead.

[+DragonsWest]

It is irresponsible to place or maintain an active cache in a location where the geocacher cannot reach it without a good chance of encountering Poison Oak, Poison Ivy, Poison Sumac, Stinging Nettles or Giant Hogweed. Many geocachers are not going to be familiar with the local flora, particularly if they are travelling from out of state.

 

I am highly sensitive to Poison Oak (Poak, in my own lingo) and have been affected by caches which not only have been in Poak infested locations, but that others who have found the cache may well have left traces of Urushiol on cache container which may be picked up by the next cacher.

 

It's a good plan to carry Tecnu, Deet or similar with you when Geocaching anywhere the plants may be. Wash hands with Tecnu and COLD water after geocaching is also a good plan.

 

Being a Cache Owner means taking the welfare of finders into consideration, not just making yet-another-hide.