<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Michael - If what you speak is true, then I have a suggestion for
Dirk...<br>
<br>
Both of my DXSpider nodes have the US Database loaded, which shows
the logged in user (almost instantaneously) the EXACT state of the
spot originator. Here's an example [last column]:<br>
<br>
<font face="Courier New">DX de W3LPL: 10107.0 VU2GSM
Heard in MA 2225Z MD<br>
DX de KD2FLY: 28120.7 LU2DO
PSK31 2225Z NY<br>
DX de K0GU: 50101.9 CE2AWW DN70MQ<>FF47FA
in/out 2226Z CO<br>
DX de K6ND: 24910.0 ZL7E QSX 24912.1 559 in
MA 2226Z MA<br>
DX de KD2JA: 24910.0 ZL7E Tnx new
one 2226Z FL<br>
DX de AD4Z: 50072.0 LU4FM/B 599 in
EL95tu 2226Z FL<br>
DX de WD4AB: 50110.0 LU5VV EL95UO<>FE48HI
57 2227Z FL</font><br>
<br>
The USDB file comes directly from the FCC database, which shows the
current 'home address on record' for each US amateur. In your
example, the following data is from the USDB file:<br>
<br>
<font face="Courier New">sh/usdb w9tvx<br>
W9TVX -> Mountain View, CA<br>
><br>
sh/usdb wa9pie<br>
WA9PIE -> Prosper, TX</font><br>
<br>
Why couldn't this same lookup process be used to correctly propagate
the CC11 line in the example?<br>
<br>
Just a thought...<br>
<br>
73, Steve - AA4U<br>
<br>
<br>
<br>
<div class="moz-cite-prefix">On 4/6/2015 9:24 AM, Michael Carper
wrote:<br>
</div>
<blockquote
cite="mid:CAKJep-AiVRYO3SZ0eAwZpSSn9yPs1Paa9+3fFOtmvx5F74idVA@mail.gmail.com"
type="cite">
<div dir="ltr">DX Spider doesn't do a "callsign lookup" when it
sends out spots. For my friends outside the US, this topic
requires a bit of detail.
<div><br>
</div>
<div>In the US, there are 10 call areas. Many many years ago,
the governing body here in the US (the FCC) forced people to
change their callsign when they moved to another call area.
But this became an administrative problem for the FCC as the
volume of people relocating in this country increased. </div>
<div><br>
</div>
<div>SO... here's the current significance of the NUMBER in a US
ham's callsign.</div>
<div>- the number is assigned from the call area that the person
lived when they were issued their first license</div>
<div>- if they move to another call area, they are not required
to change their call.</div>
<div><br>
</div>
<div>A nice map of this is at <a moz-do-not-send="true"
href="http://en.wikipedia.org/wiki/Amateur_radio_licensing_in_the_United_States">http://en.wikipedia.org/wiki/Amateur_radio_licensing_in_the_United_States</a></div>
<div><br>
</div>
<div>SO... what this means for DX Spider...</div>
<div><br>
</div>
<div>The "COUNTRY" field in the CC11 string for DX Spider is
composed of a "US State" followed by the "Country Prefix". So
in this example, we know that W9TVX is in the United States...
so the prefix "K" makes sense. But here is what I've figured
out about why it shows as "Illinois".</div>
<div><br>
</div>
<div>The US Call areas and associated States are as follows:</div>
<div>
<div>US Call Area 1 - CT,MA,ME,NH,RI,VT</div>
<div>US Call Area 2 - NJ,NY</div>
<div>US Call Area 3 - DC,DE,MD,PA</div>
<div>US Call Area 4 - AL,FL,GA,KY,NC,SC,TN,VA</div>
<div>US Call Area 5 - AR,LA,MS,NM,OK,TX</div>
<div>US Call Area 6 - CA</div>
<div>US Call Area 7 - AZ,ID,MT,NV,OR,UT,WA,WY</div>
<div>US Call Area 8 - MI,OH,WV</div>
<div>US Call Area 9 - IL,IN,WI</div>
<div>US Call Area 10 - CO,IA,KS,MN,MO,ND,NE,SD</div>
</div>
<div><br>
</div>
<div>Because clusters do not do a callsign lookup when sending a
spot to connected users, the cluster has no idea which US
State the spotted station or spotting station are in.</div>
<div><br>
</div>
<div>So... what DX Spider does is use the FIRST US State in
alphabetical order for a given callarea and sends the full
name of the state.</div>
<div><br>
</div>
<div>For example...</div>
<div><br>
</div>
<div>W9TVX... it's got a "9" in it... the first US State
(alphabetically) in the list of States in call area 9 is
"IL"... and that's "Illinois"... so let's send that one!
That's why you get <span style="font-size:12.8000001907349px">^</span><span
style="font-size:12.8000001907349px">Illinois-K^, even
though he's in California.</span></div>
<div><span style="font-size:12.8000001907349px"><br>
</span></div>
<div><span style="font-size:12.8000001907349px">If you spotted
me (WA9PIE), you would also get </span><span
style="font-size:12.8000001907349px">^</span><span
style="font-size:12.8000001907349px">Illinois-K^, even
though I live in Texas now.</span></div>
<div><span style="font-size:12.8000001907349px"><br>
</span></div>
<div><span style="font-size:12.8000001907349px">In reality, the
only States that ever get used are the first ones
alphabetically - Connecticut, New
Jersey, District-of-Columbia, Alabama, Arkansas, California,
Arizona, Michigan, Illinois, and Colorado. Regardless of
where the station is actually located, DX Spider looks at
the number in the call and grabs from these.</span></div>
<div><span style="font-size:12.8000001907349px"><br>
</span></div>
<div><span style="font-size:12.8000001907349px">Most of the
time, the US State in this field will be incorrect. Within
Ham Radio Deluxe, we offer the display of a field that
strips off the US State (because people complained about it
being wrong).</span></div>
<div><span style="font-size:12.8000001907349px"><br>
</span></div>
<div><span style="font-size:12.8000001907349px">The only fix for
this is to re-code DX Spider so that the Country field no
longer has the US State in it. However...</span></div>
<div><span style="font-size:12.8000001907349px"><br>
</span></div>
<div><span style="font-size:12.8000001907349px">If you look at
spots for other countries, you'll see that it also populates
"Secondary Administrative Districts" for other countries
too... in Canada, you'll see Provinces and Territories that
are incorrect for the same reasons.</span></div>
<div><span style="font-size:12.8000001907349px"><br>
</span></div>
<div><span style="font-size:12.8000001907349px">But anyway... a
long-winded answer. But very complete.</span></div>
<div><span style="font-size:12.8000001907349px"><br>
</span></div>
<div><span style="font-size:12.8000001907349px">Bottom line is -
the inclusion of this information into the Country field is
an "estimation" and is not related to any valid callsign
lookup information.</span></div>
<div><span style="font-size:12.8000001907349px"><br>
</span></div>
<div><span style="font-size:12.8000001907349px">Mike, WA9PIE</span></div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Apr 6, 2015 at 3:29 AM, Ian
Maude <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:maudeij@gmail.com" target="_blank">maudeij@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
I have a user who is not being shown correctly in the
cluster. He<br>
sent me the output from a test spot he sent..<br>
<br>
CC11^14262.0^W9TVX^<br>
5-Apr-2015^2332Z^TEST^W9TVX^226^226^GB7MBC^8^4^8^4^CA^CA^Illinois-K^Illinois-K^CM87^CM87<br>
<br>
W9TVX is in Mountain View CA and sh/usdb puts him in the
right place.<br>
This is happening for him even with a direct telnet to the
cluster so<br>
it would appear to not be a logging program issue. Any
thoughts would<br>
be appreciated.<br>
<br>
73 Ian<br>
<br>
_______________________________________________<br>
Dxspider-support mailing list<br>
<a moz-do-not-send="true"
href="mailto:Dxspider-support@dxcluster.org">Dxspider-support@dxcluster.org</a><br>
<a moz-do-not-send="true"
href="http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support"
target="_blank">http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a><br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Dxspider-support mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Dxspider-support@dxcluster.org">Dxspider-support@dxcluster.org</a>
<a class="moz-txt-link-freetext" href="http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support">http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a>
</pre>
</blockquote>
<br>
</body>
</html>