[Az-Geocaching] RE: Travel Bugs revisited (Ken Akerman)

RAND HARDIN listserv@azgeocaching.com
Thu, 14 Nov 2002 17:57:34 -0700


------=_NextPart_001_0001_01C28C07.4F4B7480
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

One of my biggest gripes with Travel Bugs is when someone stops by a cach=
e, picks it up and doesn't add a note, the date, and the time in the log =
book when they took it - then doesn't get to a computer to record the inf=
ormation for several days.  How many of us have gone to a cache to pick u=
p a TB only to find it missing - and then watch the cache page for severa=
l days wondering what happened to the bug?  I'm sure many of us have burn=
ed a lot of gas chasing these missing TBs.

Rand  =20
 =20
----- Original Message -----
From: RAND HARDIN
Sent: Thursday, November 14, 2002 5:12 PM
To: listserv@azgeocaching.com
Subject: Re: [Az-Geocaching] RE: Travel Bugs revisited (Ken Akerman)
 =20
Ken, =20
 =20
About the only way to solve this problem is not placing a Travel Bug in a=
 cache unless you know that you can get to a computer to log it within a =
reasonable time.
 =20
Rand =20
 =20
----- Original Message -----
From: ken@highpointer.com
Sent: Thursday, November 14, 2002 5:03 PM
To: az-geocaching@listserv.azgeocaching.com
Subject: [Az-Geocaching] RE: Travel Bugs revisited (Ken Akerman)
 =20
I wish there was a way to immediately log a cache finding and a travel bu=
g as soon as you find a cache.  When I travel, I like to find caches, and=
 particularly I like to move travel bugs that I find in caches near my ho=
me to caches as far away as possible, to put more miles on them.  However=
, when I am on the road I may not be able to get to a computer for severa=
l days.  This poses a problem for travel bugs, because someone may find t=
he travel bug before I get a chance to enter it at home or at the office.=
 =20
For example, while in Utah I put a travel bug in a cache, and while hikin=
g out I encountered the next group of local geocachers en route to the ca=
che.  I told them about the travel bug that I had put in it, and they agr=
eed not to log their travel bug finding until I had a chance to enter the=
 travel bug when I got home, which was two days later.  However, if I had=
 not encountered those geocachers on the way out, they would have picked =
up the travel bug and likely would have tried to enter it before I had a =
chance to enter it at home. =20
What can you do about delayed updates to travel bug logs, when you are on=
 the road and are away from computer access for several days or more?  Th=
is appears to be a flaw in the travel bug system. =20
Ken

------=_NextPart_001_0001_01C28C07.4F4B7480
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML><BODY STYLE=3D"font:10pt verdana; border:none;"><DIV>One of my bigg=
est gripes with Travel Bugs is when someone stops by a cache, picks it&nb=
sp;up and&nbsp;doesn't&nbsp;add a note, the date, and the time in the log=
 book&nbsp;when they took it -&nbsp;then&nbsp;doesn't get to a computer t=
o&nbsp;record the information for several days.&nbsp; How many of us have=
 gone to a cache to pick up a TB only to find it missing - and then watch=
 the&nbsp;cache page for several days wondering what happened to the bug?=
&nbsp; I'm sure many of&nbsp;us have burned a lot of gas chasing these mi=
ssing TBs.</DIV> <DIV>&nbsp;</DIV> <DIV>Rand&nbsp;&nbsp;</DIV> <DIV>&nbsp=
;</DIV> <BLOCKQUOTE style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGI=
N-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px"> <DIV sty=
le=3D"FONT: 10pt Arial">----- Original Message -----</DIV> <DIV style=3D"=
BACKGROUND: #e4e4e4; FONT: 10pt Arial; COLOR: black"><B>From:</B> RAND HA=
RDIN</DIV> <DIV style=3D"FONT: 10pt Arial"><B>Sent:</B> Thursday, Novembe=
r 14, 2002 5:12 PM</DIV> <DIV style=3D"FONT: 10pt Arial"><B>To:</B> lists=
erv@azgeocaching.com</DIV> <DIV style=3D"FONT: 10pt Arial"><B>Subject:</B=
> Re: [Az-Geocaching] RE: Travel Bugs revisited (Ken Akerman)</DIV> <DIV>=
&nbsp;</DIV> <DIV>Ken, </DIV> <DIV>&nbsp;</DIV> <DIV>About the only way t=
o solve this problem is not placing a Travel Bug in a cache unless you kn=
ow that you can get to a computer to log it within a reasonable time.</DI=
V> <DIV>&nbsp;</DIV> <DIV>Rand&nbsp;</DIV> <DIV>&nbsp;</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 Ari=
al">----- Original Message -----</DIV> <DIV style=3D"BACKGROUND: #e4e4e4;=
 FONT: 10pt Arial; COLOR: black"><B>From:</B> ken@highpointer.com</DIV> <=
DIV style=3D"FONT: 10pt Arial"><B>Sent:</B> Thursday, November 14, 2002 5=
:03 PM</DIV> <DIV style=3D"FONT: 10pt Arial"><B>To:</B> az-geocaching@lis=
tserv.azgeocaching.com</DIV> <DIV style=3D"FONT: 10pt Arial"><B>Subject:<=
/B> [Az-Geocaching] RE: Travel Bugs revisited (Ken Akerman)</DIV> <DIV>&n=
bsp;</DIV> <P>I wish there was a way to immediately log a cache finding a=
nd a travel bug as soon as you find a cache.&nbsp; When I travel, I like =
to find caches, and particularly I like to move travel bugs that I find i=
n caches near my home to caches as far away as possible, to put more mile=
s on them.&nbsp; However, when I am on the road I may not be able to get =
to a computer for several days.&nbsp; This poses a problem for travel bug=
s, because someone may find the travel bug before I get a chance to enter=
 it at home or at the office.  <P>For example, while in Utah I put a trav=
el bug in a cache, and while hiking out I encountered the next group of l=
ocal geocachers&nbsp;en route to the cache.&nbsp; I told them about the t=
ravel bug that I had put in it, and they agreed not to log their travel b=
ug finding until I had a chance to enter the travel bug when I got home, =
which was two days later.&nbsp; However, if I had not encountered those g=
eocachers on the way out, they would have picked up the travel bug and li=
kely would have tried to enter it before I had a chance to enter it at ho=
me.  <P>What can you do about delayed updates to travel bug logs, when yo=
u are on the road and are away from computer access for several days or m=
ore?&nbsp; This appears to be a flaw in the travel bug system.  <P>Ken</P=
></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------=_NextPart_001_0001_01C28C07.4F4B7480--