[Az-Geocaching] How are AZ caches determined?
Tim Giron
listserv@azgeocaching.com
Sat, 15 Mar 2003 23:05:28 -0700
--============_-1164327761==_ma============
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
>I found an out situation that appears to be an azgeocaching bug. Am
>I missing something? TheWebbman and I did a Tucson run yesterday.
>We hit 44 caches in total, including a couple along the interstate
>between Phoenix and Tucson as well as a few in the West valley.
>Here are the two oddities I noted. First, all of the caches are in
>Arizona. Most are traditional with a few being virtual, but all
>have physical coordinates well within AZ. Even so, some were marked
>as out of state on azgeocaching. Odder still, even though we hit
>all of the same caches, four of mine were tagged as out of state,
>while five were so marked for TheWebbman. Doesn't makes sense. I
>haven't yet compared the lists to see which caches didn't make the
>AZ site.
>
>Does anyone have any thoughts?
If memory serves, "members only" caches are considered "out of state"
by the azgeocaching site and I know there are a few of those down in
Tucson. As far as the discrepancy between you and The Webbman, it
looks like that is actually due to the timing of your log entries.
Were you perhaps entering them very late on Friday night and got into
the cutoff time when the azgeocaching data pull run started? If that
is the case, your numbers should square up to each other after
tonight's run.
BTW, congrats to both of you on your 2 marathon runs in the last
couple of weeks. I understand from talking to The Webbman at the
breakfast event that you are using some cool tech to optimize your
routes between caches.
Tim
Team AZFastFeet
--============_-1164327761==_ma============
Content-Type: text/html; charset="us-ascii"
<!doctype html public "-//W3C//DTD W3 HTML//EN">
<html><head><style type="text/css"><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
--></style><title>Re: [Az-Geocaching] How are AZ caches
determined?</title></head><body>
<blockquote type="cite" cite><font face="Arial" size="-1"
color="#0000FF">I found an out situation that appears to be an
azgeocaching bug. Am I missing something?
TheWebbman and I did a Tucson run yesterday. We hit 44 caches in
total, including a couple along the interstate between Phoenix and
Tucson as well as a few in the West valley. Here are the two
oddities I noted. First, all of the caches are in Arizona.
Most are traditional with a few being virtual, but all have physical
coordinates well within AZ. Even so, some were marked as out of
state on azgeocaching. Odder still, even though we hit all of
the same caches, four of mine were tagged as out of state, while five
were so marked for TheWebbman. Doesn't makes sense. I
haven't yet compared the lists to see which caches didn't make the AZ
site.</font></blockquote>
<blockquote type="cite" cite> </blockquote>
<blockquote type="cite" cite><font face="Arial" size="-1"
color="#0000FF">Does anyone have any thoughts?</font></blockquote>
<div><br></div>
<div>If memory serves, "members only" caches are considered
"out of state" by the azgeocaching site and I know there are
a few of those down in Tucson. As far as the discrepancy between
you and The Webbman, it looks like that is actually due to the timing
of your log entries. Were you perhaps entering them very late on
Friday night and got into the cutoff time when the azgeocaching data
pull run started? If that is the case, your numbers should
square up to each other after tonight's run.</div>
<div><br></div>
<div>BTW, congrats to both of you on your 2 marathon runs in the last
couple of weeks. I understand from talking to The Webbman at the
breakfast event that you are using some cool tech to optimize your
routes between caches.</div>
<div><br></div>
<div>Tim</div>
<div>Team AZFastFeet</div>
</body>
</html>
--============_-1164327761==_ma============--