[Az-Geocaching] Team Rankings

Rob Brinkerhoff listserv@azgeocaching.com
Wed, 21 Jan 2004 21:11:09 -0700


This is a multi-part message in MIME format.

------=_NextPart_000_000A_01C3E063.17547160
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Here is a question for the group. Why are teams ranked by
the total number of caches found? Would not a more valid
metric be Score (Totals of Difficulty and Terrain Ratings of
Found and Hid, as defined by azgeocaching.com)? Suppose that
there were 1005 locationless caches located in Arizona. If
one logged all 1005 locationless caches (I am not ragging on
locationless caches, just an example) and only those 1005
locationless caches they, per definition, would be the top
AZ geocaching team. The top spot could feasibly be had
without cracking open a single ammo can or peering into a
still minty fresh altoids tin!  Okay, now replace
locationless with virtuals or 1/1 urbans, a more viable
possibility. Does that really define the top caching team?
Maybe it does. Clearly some folks prefer and/or are limited
to urbans or ammo cans or locationless or puzzles or
whatever. Don't get me wrong. I am very impressed with the
routine 30+ finds in a day. I have yet to find more than 10
or 15 in a day. Though I have on several occasions spent a
full and exhausting day only to find 5 or so caches. Also on
several occasions I have spent days-on-end only to find one
cache.

Personally, I would like to see the top team ranked in terms
of Score. I think that it gives a more well-rounded view of
a teams ability. Of course that is only my opinion. What do
the rest of you folks think?

-Rob (Wily Javelina)

  ----- Original Message -----
  From: Regan L Smith
  To: listserv@azgeocaching.com
  Sent: Wednesday, January 21, 2004 8:03 PM
  Subject: Re: [Az-Geocaching] After You've Logged all the
Locationless Caches, Try This


  the newest Arizona cache is in those lines

    ----- Original Message -----
    From: Team Tierra Buena
    To: Arizona Geocaching
    Sent: Wednesday, January 21, 2004 7:36 PM
    Subject: [Az-Geocaching] After You've Logged all the
Locationless Caches, Try This


    Maybe I'm the last one to have heard about this, but I
just came across http://wwmx.org/. The World Wide Media
eXchange is a Microsoft experimental project that, among
other things is working on identifying digital photographs
by location. One way they're doing that is by providing a
free download on this site that will let you automatically
add coordinate information to your digital pix by either
dragging and dropping them onto a map or by uploading track
data from your (currently only Garmin) GPSr. It then
identifies the location of the photo by comparing the
timestamps in the track log to the timestamps in the photo
data. There's lots of other stuff like that in this site as
well.

    I haven't tried any of it, and I'm certainly not
endorsing any of it , but the site is worth a look. I
thought there were a number of interesting ideas there.

    Steve

    Team Tierra Buena


------=_NextPart_000_000A_01C3E063.17547160
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3DWord.Document name=3DProgId>
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR>
<META content=3D"Microsoft Word 10" name=3DOriginator><LINK=20
href=3D"cid:filelist.xml@01C3E054.C09E9980" rel=3DFile-List><!--[if gte =
mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:SpellingState>Clean</w:SpellingState>
  <w:GrammarState>Clean</w:GrammarState>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
  <w:Compatibility>
   <w:BreakWrappedTables/>
   <w:SnapToGridInCell/>
   <w:WrapTextWithPunct/>
   <w:UseAsianBreakRules/>
   <w:UseFELayout/>
  </w:Compatibility>
  <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
 </w:WordDocument>
</xml><![endif]-->
<STYLE>@font-face {
	font-family: SimSun;
}
@font-face {
	font-family: Book Antiqua;
}
@font-face {
	font-family: @SimSun;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; =
mso-header-margin: .5in; mso-footer-margin: .5in; mso-paper-source: 0; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 6pt; FONT-FAMILY: "Book Antiqua"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: SimSun; mso-bidi-font-family: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 6pt; FONT-FAMILY: "Book Antiqua"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: SimSun; mso-bidi-font-family: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 6pt; FONT-FAMILY: "Book Antiqua"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: SimSun; mso-bidi-font-family: "Times New Roman"
}
P.MsoEnvelopeAddress {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 6pt 2in; FONT-FAMILY: "Book Antiqua"; =
mso-pagination: widow-orphan; mso-fareast-font-family: SimSun; =
mso-bidi-font-family: Arial; mso-element: frame; =
mso-element-frame-width: 5.5in; mso-element-frame-height: 99.0pt; =
mso-element-frame-hspace: 9.0pt; mso-element-wrap: auto; =
mso-element-anchor-horizontal: page; mso-element-left: center; =
mso-element-top: bottom; mso-height-rule: exactly
}
LI.MsoEnvelopeAddress {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 6pt 2in; FONT-FAMILY: "Book Antiqua"; =
mso-pagination: widow-orphan; mso-fareast-font-family: SimSun; =
mso-bidi-font-family: Arial; mso-element: frame; =
mso-element-frame-width: 5.5in; mso-element-frame-height: 99.0pt; =
mso-element-frame-hspace: 9.0pt; mso-element-wrap: auto; =
mso-element-anchor-horizontal: page; mso-element-left: center; =
mso-element-top: bottom; mso-height-rule: exactly
}
DIV.MsoEnvelopeAddress {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 6pt 2in; FONT-FAMILY: "Book Antiqua"; =
mso-pagination: widow-orphan; mso-fareast-font-family: SimSun; =
mso-bidi-font-family: Arial; mso-element: frame; =
mso-element-frame-width: 5.5in; mso-element-frame-height: 99.0pt; =
mso-element-frame-hspace: 9.0pt; mso-element-wrap: auto; =
mso-element-anchor-horizontal: page; mso-element-left: center; =
mso-element-top: bottom; mso-height-rule: exactly
}
P.MsoEnvelopeReturn {
	FONT-SIZE: 10pt; MARGIN: 0in 0in 6pt; FONT-FAMILY: "Book Antiqua"; =
mso-pagination: widow-orphan; mso-fareast-font-family: SimSun; =
mso-bidi-font-family: Arial
}
LI.MsoEnvelopeReturn {
	FONT-SIZE: 10pt; MARGIN: 0in 0in 6pt; FONT-FAMILY: "Book Antiqua"; =
mso-pagination: widow-orphan; mso-fareast-font-family: SimSun; =
mso-bidi-font-family: Arial
}
DIV.MsoEnvelopeReturn {
	FONT-SIZE: 10pt; MARGIN: 0in 0in 6pt; FONT-FAMILY: "Book Antiqua"; =
mso-pagination: widow-orphan; mso-fareast-font-family: SimSun; =
mso-bidi-font-family: Arial
}
P.MsoSignature {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 6pt; FONT-FAMILY: "Book Antiqua"; =
mso-pagination: widow-orphan; mso-fareast-font-family: SimSun; =
mso-bidi-font-family: "Times New Roman"
}
LI.MsoSignature {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 6pt; FONT-FAMILY: "Book Antiqua"; =
mso-pagination: widow-orphan; mso-fareast-font-family: SimSun; =
mso-bidi-font-family: "Times New Roman"
}
DIV.MsoSignature {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 6pt; FONT-FAMILY: "Book Antiqua"; =
mso-pagination: widow-orphan; mso-fareast-font-family: SimSun; =
mso-bidi-font-family: "Times New Roman"
}
P.MsoSalutation {
	FONT-SIZE: 12pt; MARGIN: 12pt 0in; FONT-FAMILY: "Book Antiqua"; =
mso-pagination: widow-orphan; mso-fareast-font-family: SimSun; =
mso-bidi-font-family: "Times New Roman"; mso-style-next: Normal
}
LI.MsoSalutation {
	FONT-SIZE: 12pt; MARGIN: 12pt 0in; FONT-FAMILY: "Book Antiqua"; =
mso-pagination: widow-orphan; mso-fareast-font-family: SimSun; =
mso-bidi-font-family: "Times New Roman"; mso-style-next: Normal
}
DIV.MsoSalutation {
	FONT-SIZE: 12pt; MARGIN: 12pt 0in; FONT-FAMILY: "Book Antiqua"; =
mso-pagination: widow-orphan; mso-fareast-font-family: SimSun; =
mso-bidi-font-family: "Times New Roman"; mso-style-next: Normal
}
P.MsoDate {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 6pt; FONT-FAMILY: "Book Antiqua"; =
mso-pagination: widow-orphan; mso-fareast-font-family: SimSun; =
mso-bidi-font-family: "Times New Roman"; mso-style-next: Normal
}
LI.MsoDate {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 6pt; FONT-FAMILY: "Book Antiqua"; =
mso-pagination: widow-orphan; mso-fareast-font-family: SimSun; =
mso-bidi-font-family: "Times New Roman"; mso-style-next: Normal
}
DIV.MsoDate {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 6pt; FONT-FAMILY: "Book Antiqua"; =
mso-pagination: widow-orphan; mso-fareast-font-family: SimSun; =
mso-bidi-font-family: "Times New Roman"; mso-style-next: Normal
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; text-underline: single
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; text-underline: single
}
P.InternalAddressLine1 {
	FONT-SIZE: 12pt; MARGIN: 0.25in 0in 0pt; FONT-FAMILY: "Book Antiqua"; =
mso-pagination: widow-orphan; mso-fareast-font-family: SimSun; =
mso-bidi-font-family: "Times New Roman"; mso-style-next: Normal; =
mso-style-name: "Internal Address Line 1"
}
LI.InternalAddressLine1 {
	FONT-SIZE: 12pt; MARGIN: 0.25in 0in 0pt; FONT-FAMILY: "Book Antiqua"; =
mso-pagination: widow-orphan; mso-fareast-font-family: SimSun; =
mso-bidi-font-family: "Times New Roman"; mso-style-next: Normal; =
mso-style-name: "Internal Address Line 1"
}
DIV.InternalAddressLine1 {
	FONT-SIZE: 12pt; MARGIN: 0.25in 0in 0pt; FONT-FAMILY: "Book Antiqua"; =
mso-pagination: widow-orphan; mso-fareast-font-family: SimSun; =
mso-bidi-font-family: "Times New Roman"; mso-style-next: Normal; =
mso-style-name: "Internal Address Line 1"
}
P.InternalAddressLines {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Book Antiqua"; =
mso-pagination: widow-orphan; mso-fareast-font-family: SimSun; =
mso-bidi-font-family: "Times New Roman"; mso-style-name: "Internal =
Address Lines"
}
LI.InternalAddressLines {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Book Antiqua"; =
mso-pagination: widow-orphan; mso-fareast-font-family: SimSun; =
mso-bidi-font-family: "Times New Roman"; mso-style-name: "Internal =
Address Lines"
}
DIV.InternalAddressLines {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Book Antiqua"; =
mso-pagination: widow-orphan; mso-fareast-font-family: SimSun; =
mso-bidi-font-family: "Times New Roman"; mso-style-name: "Internal =
Address Lines"
}
P.LetterDate {
	FONT-SIZE: 12pt; MARGIN: 0.25in 0in 0.25in 4in; FONT-FAMILY: "Book =
Antiqua"; mso-pagination: widow-orphan; mso-fareast-font-family: SimSun; =
mso-bidi-font-family: "Times New Roman"; mso-style-next: "Internal =
Address Line 1"; mso-style-name: "Letter Date"
}
LI.LetterDate {
	FONT-SIZE: 12pt; MARGIN: 0.25in 0in 0.25in 4in; FONT-FAMILY: "Book =
Antiqua"; mso-pagination: widow-orphan; mso-fareast-font-family: SimSun; =
mso-bidi-font-family: "Times New Roman"; mso-style-next: "Internal =
Address Line 1"; mso-style-name: "Letter Date"
}
DIV.LetterDate {
	FONT-SIZE: 12pt; MARGIN: 0.25in 0in 0.25in 4in; FONT-FAMILY: "Book =
Antiqua"; mso-pagination: widow-orphan; mso-fareast-font-family: SimSun; =
mso-bidi-font-family: "Times New Roman"; mso-style-next: "Internal =
Address Line 1"; mso-style-name: "Letter Date"
}
P.Valediction {
	FONT-SIZE: 12pt; MARGIN: 12pt 0in 48pt; FONT-FAMILY: "Book Antiqua"; =
mso-pagination: widow-orphan; mso-fareast-font-family: SimSun; =
mso-bidi-font-family: "Times New Roman"; mso-style-next: Signature; =
mso-style-name: Valediction
}
LI.Valediction {
	FONT-SIZE: 12pt; MARGIN: 12pt 0in 48pt; FONT-FAMILY: "Book Antiqua"; =
mso-pagination: widow-orphan; mso-fareast-font-family: SimSun; =
mso-bidi-font-family: "Times New Roman"; mso-style-next: Signature; =
mso-style-name: Valediction
}
DIV.Valediction {
	FONT-SIZE: 12pt; MARGIN: 12pt 0in 48pt; FONT-FAMILY: "Book Antiqua"; =
mso-pagination: widow-orphan; mso-fareast-font-family: SimSun; =
mso-bidi-font-family: "Times New Roman"; mso-style-next: Signature; =
mso-style-name: Valediction
}
P.NormalBoldwithoutSpacing {
	FONT-WEIGHT: bold; TEXT-JUSTIFY: inter-ideograph; FONT-SIZE: 12pt; =
MARGIN: 0in 0in 0pt; FONT-FAMILY: Arial; TEXT-ALIGN: justify; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"; mso-bidi-font-family: "Times New Roman"; mso-style-name: "Normal =
Bold without Spacing"; mso-fareast-language: EN-US; =
mso-bidi-font-weight: normal
}
LI.NormalBoldwithoutSpacing {
	FONT-WEIGHT: bold; TEXT-JUSTIFY: inter-ideograph; FONT-SIZE: 12pt; =
MARGIN: 0in 0in 0pt; FONT-FAMILY: Arial; TEXT-ALIGN: justify; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"; mso-bidi-font-family: "Times New Roman"; mso-style-name: "Normal =
Bold without Spacing"; mso-fareast-language: EN-US; =
mso-bidi-font-weight: normal
}
DIV.NormalBoldwithoutSpacing {
	FONT-WEIGHT: bold; TEXT-JUSTIFY: inter-ideograph; FONT-SIZE: 12pt; =
MARGIN: 0in 0in 0pt; FONT-FAMILY: Arial; TEXT-ALIGN: justify; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"; mso-bidi-font-family: "Times New Roman"; mso-style-name: "Normal =
Bold without Spacing"; mso-fareast-language: EN-US; =
mso-bidi-font-weight: normal
}
SPAN.EmailStyle27 {
	FONT-WEIGHT: normal; COLOR: windowtext; FONT-STYLE: normal; =
FONT-FAMILY: "Book Antiqua"; TEXT-DECORATION: none; text-underline: =
none; mso-style-type: personal-compose; mso-style-noshow: yes; =
mso-ansi-font-size: 12.0pt; mso-bidi-font-size: 12.0pt; =
mso-ascii-font-family: "Book Antiqua"; mso-hansi-font-family: "Book =
Antiqua"; text-line-through: none
}
SPAN.SpellE {
	mso-style-name: ""; mso-spl-e: yes
}
SPAN.GramE {
	mso-style-name: ""; mso-gram-e: yes
}
DIV.Section1 {
	page: Section1
}
</STYLE>
<!--[if gte mso 10]>
<style>
 /* Style Definitions */=20
 table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman";}
</style>
<![endif]--></HEAD>
<BODY lang=3DEN-US style=3D"tab-interval: .5in" vLink=3Dpurple =
link=3Dblue=20
bgColor=3D#ffffff>
<DIV><FONT face=3DVerdana size=3D2>Here is a question for the group. Why =
are teams=20
ranked by the total number of caches found? Would not a more valid =
metric be=20
Score (Totals of Difficulty and Terrain Ratings of Found and Hid, as =
defined=20
by&nbsp;azgeocaching.com)? Suppose that there were 1005 locationless =
caches=20
located in Arizona. If one logged all 1005 locationless caches&nbsp;(I =
am not=20
ragging on&nbsp;locationless caches, just an example) and&nbsp;only =
those 1005=20
locationless caches they, per definition, would be the top AZ geocaching =
team.=20
The top spot could <FONT size=3D2>feasibly&nbsp;</FONT>be had without =
cracking=20
open a single ammo can or peering into a still minty fresh altoids=20
tin!&nbsp;&nbsp;Okay, now replace locationless with virtuals or =
1/1&nbsp;urbans,=20
a more viable possibility.&nbsp;Does that really define the top caching =
team?=20
&nbsp;Maybe it does. Clearly some folks prefer and/or=20
are&nbsp;limited&nbsp;to&nbsp;urbans or ammo cans or locationless or =
puzzles or=20
whatever. Don't get me wrong. I am very impressed with the routine 30+ =
finds in=20
a day. I have yet to find more than 10 or 15 in a day.&nbsp;Though I =
have on=20
several occasions&nbsp;spent a full and exhausting day only to find 5 or =
so=20
caches. Also on several occasions I have spent days-on-end only to find =
one=20
cache.&nbsp;</FONT></DIV>
<DIV><FONT face=3DVerdana size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DVerdana size=3D2>Personally, I would like to see the =
top team=20
ranked in terms of Score. I think that it gives a more well-rounded view =
of a=20
teams ability. Of course that is only my opinion. What do the rest of =
you folks=20
think?</FONT></DIV>
<DIV><FONT face=3DVerdana size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DVerdana size=3D2>-Rob (Wily Javelina)</FONT></DIV>
<DIV><FONT face=3DVerdana size=3D2></FONT>&nbsp;</DIV>
<BLOCKQUOTE dir=3Dltr=20
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=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A title=3Dbuggers@mindspring.com =
href=3D"mailto:buggers@mindspring.com">Regan L=20
  Smith</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Dlistserv@azgeocaching.com=20
  =
href=3D"mailto:listserv@azgeocaching.com">listserv@azgeocaching.com</A> =
</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Wednesday, January 21, =
2004 8:03=20
  PM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: [Az-Geocaching] =
After You've=20
  Logged all the Locationless Caches, Try This</DIV>
  <DIV><FONT face=3DVerdana size=3D2></FONT><BR></DIV>
  <DIV><FONT face=3DArial size=3D2>the newest Arizona cache is in those=20
  lines</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <BLOCKQUOTE dir=3Dltr=20
  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=20
    style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
    <A title=3Dteamtierrabuena@earthlink.net=20
    href=3D"mailto:teamtierrabuena@earthlink.net">Team Tierra Buena</A> =
</DIV>
    <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A=20
    title=3Daz-geocaching@listserv.azgeocaching.com=20
    href=3D"mailto:az-geocaching@listserv.azgeocaching.com">Arizona =
Geocaching</A>=20
    </DIV>
    <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Wednesday, January 21, =
2004 7:36=20
    PM</DIV>
    <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> [Az-Geocaching] =
After You've=20
    Logged all the Locationless Caches, Try This</DIV>
    <DIV><BR></DIV>
    <DIV class=3DSection1>
    <P class=3DMsoNormal><FONT face=3D"Book Antiqua" size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt">Maybe I=92m the last one to have heard =
about this, but=20
    I just came across <A =
href=3D"http://wwmx.org/">http://wwmx.org/</A>. The=20
    World Wide Media eXchange is a Microsoft experimental project that, =
among=20
    other things is working on identifying digital photographs by =
location. One=20
    way they=92re doing that is by providing a free download on this =
site that=20
    will let you automatically add coordinate information to your =
digital pix by=20
    either dragging and dropping them onto a map or by uploading track =
data from=20
    your (currently only Garmin) GPSr. It then identifies the location =
of the=20
    photo by comparing the timestamps in the track log to the timestamps =
in the=20
    photo data. There=92s lots of other stuff like that in this site as=20
    well.<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3D"Book Antiqua" size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt">I haven=92t tried any of it, and I=92m =
certainly not=20
    endorsing any of <SPAN class=3DGramE>it ,</SPAN> but the site is =
worth a look.=20
    I thought there were a number of interesting ideas=20
    there.<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3D"Book Antiqua" size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt">Steve<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3D"Book Antiqua" size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt">Team Tierra Buena=20
  =
<o:p></o:p></SPAN></FONT></P></DIV></BLOCKQUOTE></BLOCKQUOTE></BODY></HTM=
L>

------=_NextPart_000_000A_01C3E063.17547160--