[Az-Geocaching] Problems with location based identifier

Mon, 17 Mar 2003 13:57:12 -0700

This is a multi-part message in MIME format.

------=_NextPart_000_00D2_01C2EC8D.1CC98D30
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Yup, I agree.  (Believe it or not, by contradicting my own thoughts)  I
guess my point was that I believe that perhaps one character of the new code
could be reserved for SOME type of identifier to help you quickly learn
something about it.  The state/country example was weak, I just wanted to
get everyone thinking along these lines to see if anything else came to
mind.

To help understand my thought, consider this:  I don't know how many times I
was driving, saw a waypoint pop up on my screen,  stopped for fun to see
what it was... After searching around for a bit I got disappointed, then
returned to the Internet only to find out that it was a locationless or
"puzzle" based cache that did not exist there.  A simple character in the
wapyoint number would have alerted me to this before I considered stopping.
Just a thought.

TheWebbman
Webb Pickersgill
  -----Original Message-----
  From: az-geocaching-admin@listserv.azgeocaching.com
[mailto:az-geocaching-admin@listserv.azgeocaching.com]On Behalf Of
ken@highpointer.com
  Sent: Monday, March 17, 2003 12:49 PM
  To: listserv@azgeocaching.com
  Subject: [Az-Geocaching] Problems with location based identifier

  Another possibility (location based identifier): Reserve the first 2
characters as location indicators: AZ, PA, TX (states)  and CH, IL, DU, RU
(countries, etc.)  This does however unfairly limit the number of caches
within a state or country.  As we all know, AZ would probably need more
numbers than RI. ;)

  I don't think that will work very well.   You have correctly pointed out
that large states may use up their allotment of numbers relatively soon,
while small states may never use up their allotment of numbers.  For
example, Colorado used to assign license plate numbers based on the county
that the vehicle was registered in, but abandoned that policy because urban
counties have populations over 100,000 and thus were using up their allotted
numbers, whereas some rural counties have under 1,000 people and thus used
only a small percentage of their alloted characters.

  Also, some countries codes you listed are the same as states - IL is also
the abbreviation for Illinois, for example.

  Ken (a.k.a. Highpointer)

------=_NextPart_000_00D2_01C2EC8D.1CC98D30
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">

<META content=3D"MSHTML 6.00.2723.2500" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D576305220-17032003><FONT face=3DArial color=3D#0000ff =
size=3D2>Yup, I=20
agree.&nbsp; (Believe it or not, by contradicting my own thoughts)&nbsp; =
I guess=20
my point was that I believe that perhaps one character of the new code =
could be=20
reserved for SOME type of identifier to help you quickly learn something =
about=20
it.&nbsp; The state/country example was weak, I just wanted to get =
everyone=20
thinking along these lines to see if anything else came to=20
mind.</FONT></SPAN></DIV>
<DIV><SPAN class=3D576305220-17032003><FONT face=3DArial color=3D#0000ff =

size=3D2>&nbsp;</DIV>
<DIV>To=20
help understand my thought, consider this:&nbsp; I don't know how many =
times I=20
was driving, saw a waypoint pop up on my screen,&nbsp; stopped for fun =
to see=20
what it was... After searching around for a bit I got disappointed, then =

returned to the Internet only to find out that it was a locationless or =
"puzzle"=20
based cache that did not exist there.&nbsp; A simple character in the =
wapyoint=20
number would have alerted me to this before I considered stopping.&nbsp; =
Just a=20
thought.</FONT></SPAN></DIV>
<DIV><SPAN class=3D576305220-17032003><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D576305220-17032003><FONT face=3DArial color=3D#0000ff =

size=3D2>TheWebbman</DIV>
<DIV>Webb=20
Pickersgill</DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
 <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft>-----Original Message----- From:=20
 az-geocaching-admin@listserv.azgeocaching.com=20
 [mailto:az-geocaching-admin@listserv.azgeocaching.com]On Behalf Of=20
 ken@highpointer.com Sent: Monday, March 17, 2003 12:49=20
 PM To: listserv@azgeocaching.com Subject: =
[Az-Geocaching]=20
 Problems with location based identifier </DIV>
 Another possibility (location based identifier): Reserve the =
first 2=20
 characters as location indicators: AZ, PA, TX (states)&nbsp; and CH, =
IL, DU,=20
 RU (countries, etc.)&nbsp; This does however unfairly limit the number =
of=20
 caches within a state or country.&nbsp; As we all know, AZ would =
probably need=20
 more numbers than RI. ;)
 I don't think that will work very well.&nbsp;&nbsp; You have =
correctly=20
 pointed out that large states may use up their allotment of numbers =
relatively=20
 soon, while small states may never use up their allotment of =
numbers.&nbsp;=20
 For example, Colorado used to assign license plate numbers based on =
the county=20
 that the vehicle was registered in, but abandoned that policy because =
urban=20
 counties have populations over 100,000 and thus were using up their =
allotted=20
 numbers, whereas some rural counties have under 1,000 people and thus =
used=20
 only a small percentage of their alloted characters.
 Also, some countries codes&nbsp;you listed are the same as states - =
IL is=20
 also the abbreviation for Illinois, for example.
 Ken (a.k.a.=20
Highpointer)</BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_00D2_01C2EC8D.1CC98D30--