I just realized that there IS a way to do this, but it involves sharing information derived from Pocket Queries, which is expressly forbidden by the TOS.
We certainly don't want to go there, now do we?
-----Original Message-----
From: Team Nine Lives
Date: 1/11/07 10:47
To: listserv@azgeocaching.com
Subj: Re: [Az-Geocaching] finding geocaches that neither of two (or more) teams have found
Yeah, we do both those. Usually I'm last to find, which is great
entertainment for the others.
But it would be nice to be able to plan a target-rich environment for the
group. I know some of you have to go to new area codes to find a new GC, so
you have no sympathy.
The refinds can be entertaining too, especially when containers are
switched, or "drift" to a new location, or the weather / plants / time of
day/night have changed, creating entirely new challenges.
On 1/11/07, AZcachemeister <
azcachemeister@getnet.com> wrote:
>
> Or.. heaven forbid, stop and let your friend find a cache you have
> already found while you get to laugh at (er.. with) them.
>
> This is the proper course of action. Sometimes, after the searching team
> comes up empty, the previous finders get to say 'I KNOW it was RIGHT HERE!
> Looks like it is missing.' And the owner gets solid confirmation that their
> cache definitely has a problem.
>
>
> ShadowAce wrote:
>
> We normally do the 'Next is.. ' 'Already got it' 'ok, next is...'
>
> Or.. heaven forbid, stop and let your friend find a cache you have
> already found while you get to laugh at (er.. with) them.
>
> On 1/10/07, Team Nine Lives <teamninelives@gmail.com> wrote:
> >
> > Sometimes we go out geocaching with friends. When we do this we'd like
> > to prepare a list of caches that neither of us have found already. What's
> > the easiest way to do this? (If pocket queries allowed "Not found by Team_A
> > AND not found by Team_B, that would be perfect but I'm not aware of how to
> > do this.)
> >
> > Currently we are doing pocket queriies and manually plucking stuff out
> > of them within cmconvert before saving the modified file as a new .gpx and
> > .pdb for GPSWatcher and our Palm PDA's, respectively. (We've each had some
> > nonpositive experiences with the GSAK / Borg installation assuming control
> > of most of our computer systems ;-).
> >
> > Brad, Team Nine Lives
> >
> >
> > ____________________________________________________________
> > Az-Geocaching mailing list listserv@azgeocaching.com
> > To edit your setting, subscribe or unsubscribe visit:
> > http://listserv.azgeocaching.com/mailman/listinfo/az-geocaching
> >
> > Arizona's Geocaching Resource
> > http://www.azgeocaching.com
> >
> >
____________________________________________________________
Az-Geocaching mailing list
listserv@azgeocaching.com
To edit your setting, subscribe or unsubscribe visit:
http://listserv.azgeocaching.com/mailman/listinfo/az-geocaching
Arizona's Geocaching Resource
http://www.azgeocaching.com
(text/plain)