<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=utf-8" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.23588">
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2 face=Arial>The cluster does a USDB lookup for <FONT
color=#ff0000>all</FONT> US and VE calls. The spotter and dx state fields
for W9TVX are both shown as CA, which is correct. The problem is the CQ
and ITU zones appear to derived from the call prefix. The zone fields
are all wrong. They should be 6 and 3, not 8 and 4 as shown.
The country is also determined by the call prefix. A KH6 in TX will
give a CC11 string of CA for the state and Hawaii for the country and wrong
zones. Spots for W4s in FL also give the wrong CQ zone as Spider thinks
all W4s are in CQ zone 4. There are many more US prefixes where the wrong
zones are given.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>CC11^18074.1^KH6MB^
7-Apr-2015^1637Z^^IK6SNR^112^85^IZ8BRI-2^<FONT color=#ff0000>61</FONT>^<FONT
color=#ff0000>31</FONT>^28^15^<FONT color=#ff0000>TX</FONT>^^<FONT
color=#ff0000>Hawaii-KH6</FONT>^Abruzzo-Marche-I^BL11^JN62</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Lee VE7CC</FONT></DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="FONT: 10pt arial; BACKGROUND: #e4e4e4; font-color: black"><B>From:</B>
<A title=mike@wa9pie.net href="mailto:mike@wa9pie.net">Michael Carper</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A
title=dxspider-support@dxcluster.org
href="mailto:dxspider-support@dxcluster.org">The DXSpider Support list</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Wednesday, April 08, 2015 10:35
AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [Dxspider-support] Incorrect
User details</DIV>
<DIV><BR></DIV>
<DIV dir=ltr>To be clear... the UCDB 'may be' where the stand-alone STATE
fields in the CC11 string are populated. But the STATE in the COUNTRY
field is certainly not populated that way. I think the information in
the COUNTRY field were at the core of Ian's question.
<DIV><BR></DIV>
<DIV>The problem with populating the STATE in the COUNTRY field with USDB data
is that it's US specific. In other words - that field contains the
"Primary Administrative Subdivision" (see <A
href="http://www.adif.org">www.adif.org</A>) information for ALL countries -
not just the United States. So correcting this problem with regards to
the COUNTRY field in the CC11 string may cause problems with the way the
"Primary Administrative Subdivision" is populated for 'other countries'.</DIV>
<DIV><BR></DIV>
<DIV>If I were to make a suggestion...</DIV>
<DIV><BR></DIV>
<DIV>I'd (a) remove the "Primary Administrative Subdivision" from the COUNTRY
field in the CC11 string, have it show only country or country prefix, and (b)
populate the "STATE" fields with the "code" for the "Primary Administrative
Subdivisions" for all countries.</DIV>
<DIV><BR></DIV>
<DIV>Mike, WA9PIE</DIV></DIV>
<DIV class=gmail_extra><BR>
<DIV class=gmail_quote>On Mon, Apr 6, 2015 at 6:50 PM, Mike McCarthy, W1NR
<SPAN dir=ltr><<A href="mailto:lists@w1nr.net"
target=_blank>lists@w1nr.net</A>></SPAN> wrote:<BR>
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>Actually, USDB is used for both spotter and spotted
callsigns but I<BR>don't think it goes along in the normal PC11 messages
between clusters<BR>and is looked up each time from each clusters
database.<BR><BR>The issue is where the CC11 comes from. I am no expert on
the protocols,<BR>but I think CC11 is from a user application. It is
possible that it was<BR>derived from an outdated buckmaster database on some
spotters computer.<BR><BR>Mike, W1NR<BR>
<DIV>
<DIV class=h5><BR>On 04/06/2015 06:40 PM, Steve Carroll - AA4U
wrote:<BR>> 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<BR>> logged in user (almost instantaneously) the
EXACT state of the spot<BR>> originator. Here's an example [last
column]:<BR>><BR>> DX de W3LPL: 10107.0
VU2GSM Heard in MA<BR>> 2225Z MD<BR>> DX de
KD2FLY: 28120.7 LU2DO
PSK31<BR>> 2225Z NY<BR>> DX de K0GU: 50101.9
CE2AWW DN70MQ<>FF47FA in/out<BR>> 2226Z
CO<BR>> DX de K6ND: 24910.0 ZL7E
QSX 24912.1 559 in MA<BR>> 2226Z MA<BR>> DX de
KD2JA: 24910.0 ZL7E
Tnx new one<BR>> 2226Z FL<BR>> DX de AD4Z:
50072.0 LU4FM/B 599 in EL95tu<BR>> 2226Z
FL<BR>> DX de WD4AB: 50110.0 LU5VV
EL95UO<>FE48HI 57<BR>> 2227Z FL<BR>><BR>> The
USDB file comes directly from the FCC database, which shows the<BR>>
current 'home address on record' for each US amateur. In your
example,<BR>> the following data is from the USDB file:<BR>><BR>>
sh/usdb w9tvx<BR>> W9TVX -> Mountain View,
CA<BR>>><BR>> sh/usdb wa9pie<BR>> WA9PIE -> Prosper,
TX<BR>><BR>> Why couldn't this same lookup process be used to
correctly propagate the<BR>> CC11 line in the example?<BR>><BR>>
Just a thought...<BR>><BR>> 73, Steve -
AA4U<BR>><BR>><BR>><BR>> On 4/6/2015 9:24 AM, Michael Carper
wrote:<BR>>> DX Spider doesn't do a "callsign lookup" when it sends
out spots. For<BR>>> my friends outside the US, this topic
requires a bit of detail.<BR>>><BR>>> In the US, there are 10
call areas. Many many years ago, the<BR>>> governing body here
in the US (the FCC) forced people to change their<BR>>> callsign when
they moved to another call area. But this became an<BR>>>
administrative problem for the FCC as the volume of people
relocating<BR>>> in this country increased.<BR>>><BR>>>
SO... here's the current significance of the NUMBER in a US
ham's<BR>>> callsign.<BR>>> - the number is assigned from the
call area that the person lived when<BR>>> they were issued their
first license<BR>>> - if they move to another call area, they are not
required to change<BR>>> their call.<BR>>><BR>>> A nice
map of this is<BR>>> at <A
href="http://en.wikipedia.org/wiki/Amateur_radio_licensing_in_the_United_States"
target=_blank>http://en.wikipedia.org/wiki/Amateur_radio_licensing_in_the_United_States</A><BR>>><BR>>>
SO... what this means for DX Spider...<BR>>><BR>>> The "COUNTRY"
field in the CC11 string for DX Spider is composed of a<BR>>> "US
State" followed by the "Country Prefix". So in this example,
we<BR>>> know that W9TVX is in the United States... so the prefix "K"
makes<BR>>> sense. But here is what I've figured out about why
it shows as<BR>>> "Illinois".<BR>>><BR>>> The US Call
areas and associated States are as follows:<BR>>> US Call Area 1 -
CT,MA,ME,NH,RI,VT<BR>>> US Call Area 2 - NJ,NY<BR>>> US Call
Area 3 - DC,DE,MD,PA<BR>>> US Call Area 4 -
AL,FL,GA,KY,NC,SC,TN,VA<BR>>> US Call Area 5 -
AR,LA,MS,NM,OK,TX<BR>>> US Call Area 6 - CA<BR>>> US Call Area 7
- AZ,ID,MT,NV,OR,UT,WA,WY<BR>>> US Call Area 8 - MI,OH,WV<BR>>>
US Call Area 9 - IL,IN,WI<BR>>> US Call Area 10 -
CO,IA,KS,MN,MO,ND,NE,SD<BR>>><BR>>> Because clusters do not do a
callsign lookup when sending a spot to<BR>>> connected users, the
cluster has no idea which US State the spotted<BR>>> station or
spotting station are in.<BR>>><BR>>> So... what DX Spider does
is use the FIRST US State in alphabetical<BR>>> order for a given
callarea and sends the full name of the state.<BR>>><BR>>> For
example...<BR>>><BR>>> W9TVX... it's got a "9" in it... the
first US State (alphabetically)<BR>>> in the list of States in call
area 9 is "IL"... and that's<BR>>> "Illinois"... so let's send that
one! That's why you<BR>>> get ^Illinois-K^, even though he's in
California.<BR>>><BR>>> If you spotted me (WA9PIE), you would
also get ^Illinois-K^, even<BR>>> though I live in Texas
now.<BR>>><BR>>> In reality, the only States that ever get used
are the first ones<BR>>> alphabetically - Connecticut, New Jersey,
District-of-Columbia,<BR>>> Alabama, Arkansas, California, Arizona,
Michigan, Illinois, and<BR>>> Colorado. Regardless of where the
station is actually located, DX<BR>>> Spider looks at the number in
the call and grabs from these.<BR>>><BR>>> Most of the time, the
US State in this field will be incorrect.<BR>>> Within Ham Radio
Deluxe, we offer the display of a field that strips<BR>>> off the US
State (because people complained about it being
wrong).<BR>>><BR>>> The only fix for this is to re-code DX
Spider so that the Country<BR>>> field no longer has the US State in
it. However...<BR>>><BR>>> If you look at spots for other
countries, you'll see that it also<BR>>> populates "Secondary
Administrative Districts" for other countries<BR>>> too... in Canada,
you'll see Provinces and Territories that are<BR>>> incorrect for the
same reasons.<BR>>><BR>>> But anyway... a long-winded
answer. But very complete.<BR>>><BR>>> Bottom line is -
the inclusion of this information into the Country<BR>>> field is an
"estimation" and is not related to any valid callsign<BR>>> lookup
information.<BR>>><BR>>> Mike, WA9PIE<BR>>><BR>>> On
Mon, Apr 6, 2015 at 3:29 AM, Ian Maude <<A
href="mailto:maudeij@gmail.com">maudeij@gmail.com</A><BR></DIV></DIV><SPAN>>>
<mailto:<A href="mailto:maudeij@gmail.com">maudeij@gmail.com</A>>>
wrote:<BR>>><BR>>> 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></SPAN>>>
<A
href="mailto:Dxspider-support@dxcluster.org">Dxspider-support@dxcluster.org</A>
<mailto:<A
href="mailto:Dxspider-support@dxcluster.org">Dxspider-support@dxcluster.org</A>><BR>
<DIV class=HOEnZb>
<DIV class=h5>>> <A
href="http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support"
target=_blank>http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</A><BR>>><BR>>><BR>>><BR>>><BR>>>
_______________________________________________<BR>>> Dxspider-support
mailing list<BR>>> <A
href="mailto:Dxspider-support@dxcluster.org">Dxspider-support@dxcluster.org</A><BR>>>
<A href="http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support"
target=_blank>http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</A><BR>><BR>><BR>><BR>>
_______________________________________________<BR>> Dxspider-support
mailing list<BR>> <A
href="mailto:Dxspider-support@dxcluster.org">Dxspider-support@dxcluster.org</A><BR>>
<A href="http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support"
target=_blank>http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</A><BR>><BR><BR>_______________________________________________<BR>Dxspider-support
mailing list<BR><A
href="mailto:Dxspider-support@dxcluster.org">Dxspider-support@dxcluster.org</A><BR><A
href="http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support"
target=_blank>http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</A><BR></DIV></DIV></BLOCKQUOTE></DIV><BR></DIV>
<P>
<HR>
<P></P>_______________________________________________<BR>Dxspider-support
mailing
list<BR>Dxspider-support@dxcluster.org<BR>http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support<BR></BLOCKQUOTE></BODY></HTML>