[Az-Geocaching] No Tresspassing Signs
RAND HARDIN
listserv@azgeocaching.com
Mon, 16 Feb 2004 18:58:27 -0700
------=_NextPart_001_0001_01C3F4BE.DC8B8300
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Denny,
Glad to see that you're still around! Missed your caches and input.
You're correct in posting your note on the cache page about the "NO TRESS=
PASSING" signs at the cache site. We as geocachers have a responsibility=
to be sure that the rules are followed.
The cache, "A Brick In Stalingrad" (GCE770) is almost 11 months old and h=
as 70 logs. I was the second visitor to the cache and I remember it well=
I had to park around the corner from the park due to "no parking" bein=
g allowed on the main street next to the cache site. I believe the park =
was fairly new at the time of the cache placement. I know that if I had =
seen a "NO TRESSPASSING" sign I would have posted a note on the cache pag=
e. I know that other high profile cachers would have done the same. It'=
s possible that the signs were not posted until recently. =20
Since there are "NO TRESSPASSING" signs posted at the park, I agree with =
your note for the cache to be archived.
Rand (RandMan) =20
----- Original Message -----
From: Ford, Denny
Sent: Monday, February 16, 2004 4:24 PM
To: 'listserv@azgeocaching.com'
Subject: [Az-Geocaching] No Tresspassing Signs
I know that I have been out of the loop in Geocaching for a while, but s=
ince when is it ok to place a cache in an area clearly marked NO Trespass=
ing. Refer to cache GCE770- A Brick In Stalingrad. I tried to visit thi=
s cache on January 31st, and within 200 feet of where the cache should ha=
ve been was not one but two NO Trespassing signs. I am sorry but this is=
what gives Geocachers a bad name, as bad as the Geotrashers we were labe=
l by the Arizona Repulsive article. Am I totally off base? This one hap=
pened to be on my way home, but if this would have been out where I drove=
miles to get to it and find out it was on private property I would have =
been irritated to say the least. I have seen a few caches lately place =
in community areas where the No Trespassing signs say for residents of HO=
A only but no permissions are posted on the websites. I want to hear the=
feelings of others .
Ok I am down from my soap box, and have taken long breaths and counted to=
10.
Annoyed Tres Hombre
Denny
------=_NextPart_001_0001_01C3F4BE.DC8B8300
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<HTML><BODY STYLE=3D"font:10pt verdana; border:none;"><DIV>Denny,</DIV> <=
DIV> </DIV> <DIV>Glad to see that you're still around! Missed =
your caches and input.</DIV> <DIV> </DIV> <DIV>You're correct in pos=
ting your <EM>note</EM> on the cache page about the "NO TRESSPASSING" sig=
ns at the cache site. We as geocachers have a responsibility to be =
sure that the rules are followed.</DIV> <DIV> </DIV> <DIV>The cache,=
<STRONG>"A Brick In Stalingrad"</STRONG> <STRONG>(GCE770)</STRONG> =
is almost 11 months old and has 70 logs. I was the second visitor t=
o the cache and I remember it well. I had to park around the c=
orner from the park due to "no parking" being allowed on the main st=
reet next to the cache site. I believe the park was fairly new at t=
he time of the cache placement. I know that if I had seen a "NO TRE=
SSPASSING" sign I would have posted a note on the cache page. I kno=
w that other high profile cachers would have done the same. It's po=
ssible that the signs were not posted until recently. </DIV> <DIV>&=
nbsp;</DIV> <DIV>Since there are "NO TRESSPASSING" signs posted at the pa=
rk, I agree with your <EM>note</EM> for the cache to be ar=
chived.</DIV> <DIV> </DIV> <DIV>Rand (RandMan) </DIV> <DI=
V> </DIV> <BLOCKQUOTE style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px=
; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px"> <=
DIV style=3D"FONT: 10pt Arial">----- Original Message -----</DIV> <DIV st=
yle=3D"BACKGROUND: #e4e4e4; FONT: 10pt Arial; COLOR: black"><STRONG>From:=
Ford, Denny</STRONG></DIV> <DIV style=3D"FONT: 10pt Arial"><B>Sent:</B> =
Monday, February 16, 2004 4:24 PM</DIV> <DIV style=3D"FONT: 10pt Arial"><=
B>To:</B> 'listserv@azgeocaching.com'</DIV> <DIV style=3D"FONT: 10pt Aria=
l"><B>Subject:</B> [Az-Geocaching]<STRONG> No Tresspassing Signs</STRONG>=
</DIV> <DIV> </DIV> <META content=3D"MSHTML 6.00.2800.1276" name=3DG=
ENERATOR> <DIV><FONT face=3DArial size=3D2><SPAN class=3D937424822-160220=
04> I know that I have been out of the loop in Geocaching for a whil=
e, <U>but since when is it ok to place a</U> <U>cache in an area clearly =
marked NO Trespassing</U>. <STRONG>Refer to cache GCE770- A Brick I=
n Stalingrad</STRONG>. I tried to visit this cache on January 31st,=
and within 200 feet of where the cache should have been was not one but =
two NO Trespassing signs. I am sorry but this is what gives Geocach=
ers a bad name, as bad as the Geotrashers we were label by the Arizona Re=
pulsive article. Am I totally off base? This one happened to =
be on my way home, but if this would have been out where I drove miles to=
get to it and find out it was on private property I would have been irri=
tated to say the least. I have seen a few caches lately place=
in community areas where the No Trespassing signs say for residents of H=
OA only but no permissions are posted on the websites. I want to he=
ar the feelings of others .</SPAN></FONT></DIV> <DIV><FONT face=3DArial s=
ize=3D2><SPAN class=3D937424822-16022004></SPAN></FONT> </DIV> <DIV>=
<FONT face=3DArial size=3D2><SPAN class=3D937424822-16022004>Ok I am down=
from my soap box, and have taken long breaths and counted to 10.</SPAN><=
/FONT></DIV> <DIV><FONT face=3DArial size=3D2><SPAN class=3D937424822-160=
22004></SPAN></FONT> </DIV> <DIV><FONT face=3DArial size=3D2><SPAN c=
lass=3D937424822-16022004>Annoyed Tres Hombre</SPAN></FONT></DIV> <DIV><F=
ONT face=3DArial size=3D2><SPAN class=3D937424822-16022004></SPAN></FONT>=
</DIV> <DIV><FONT face=3DArial size=3D2><SPAN class=3D937424822-160=
22004>Denny</SPAN></FONT></DIV></BLOCKQUOTE></BODY></HTML>
------=_NextPart_001_0001_01C3F4BE.DC8B8300--