[LOGic] [logic_software] Re: DX OR PREFIX TABLE ERROR

Wed Jan 12 04:26:32 EST 2011

Dan,

Both Minami Torishima and Ogasawara use 'JD1' both as a callsign prefix and
as a portable identifier. To my knowledge there is no way to uniquely
determine these two DXCC entities only by the callsign. In looking at my
log about half of all contacts on JD1-O and JD1-M were using the portable
identifier with JA callsign/JD1. Note that the ARRL lists both entities as
JD1.

Also, I found no 'JD' callsigns in my log (out of close to 5000 JA QSOs)
which were in Japan proper. All were on JD1-O or JD1-M. It appears that
the JA government assigns 'JD' prefixes only to these two island groups.
I've also worked a JARL special event station (8N1OGA) on Ogasawara so keep
alert for these operations.

So the LOGic prefix table is correct. You could always edit the prefix
table in advance when an operation is announced so the spots would pop up
correctly. It's easier to just work the JD1 and get it resolved later.

Good luck catching JD1-M!

73, Greg, K7KJ

 _____ 
From: K0DAN [mailto:k0dan at arrl.net] 
Sent: Tuesday, January 11, 2011 4:01 PM
To: logic_software at yahoogroups.com; logic at mailman.qth.net
Cc: dh at hosenose.com
Subject: [logic_software] Re: DX OR PREFIX TABLE ERROR

Thanks to those who responded to my inquiry, and confirmed what I suspected,
that JD1BMH is Ogasawara.

What I *should have asked* is what LOGic's Prefix Table SHOULD look like?

Mine has the following entries for JD1-M and JD1-O:

JD1-M JD1-M, JD1 Minami-tori-shima
JD1-O JD1-O, JD1 Volcano Is Group
(and also generic JA also includes JD)

So JD1BMH, the ham I worked, could have been in any of these DXCC island
groups, or anywhere in Japan for that matter. Which means the next rare
entity could be missed by LOGic and incorrectly placed.

Can this be massaged out of the Prefix Table, or is this another licensing
inconsistency which originates with Japan's licensing authority? I have
JD1BMH properly placed in JD1-O, but am thinking about the next rare one....

Thanks and 73

Dan
K0DAN
----- Original Message ----- 
From: K0DAN <mailto:k0dan at comcast.net> 
To: logic_software at yahoogroups.com ; logic at mailman.qth.net 
Cc: dh at hosenose.com 
Sent: Tuesday, January 11, 2011 12:55 PM
Subject: DX OR PREFIX TABLE ERROR

Hi LOGic group, I'd like some assistance to determine if I worked a rare DX
prefix I've been chasing, or have a long-standing prefix table problem?

I recently worked JD1BMH, as he was in my WANTED list as MINAMI TORISHIMA
(JD1-M).

My PREFIX TABLE (probably the original that came with LOGic 4, and manually
modified over the years) shows some conflicts with MINAMI TORISHIMA (MARCUS
ISLAND?), VOLCANO ISLANDS GROUP (OGASAWARA - BONIN ISLAND).

The web page for JD1BMH suggests Ogasawara.

Some of the LOGic users are religious about keeping their Prefix Table
current (I try to but, but....)... 

Would someone help me with the reality of the correct Prefix Table, and in
so-doing advise if I have worked a new entity to my DXCC lists?

Thanks and 73

Dan
K0DAN
__._,_.___

<http://geo.yahoo.com/serv?s=97476590/grpId=16829777/grpspId=1705063108/msgI
d=493/stime=1294792984> 
Your email settings: Individual Email|Traditional 
Change
<http://groups.yahoo.com/group/logic_software/join;_ylc=X3oDMTJncTlidmFiBF9T
Azk3NDc2NTkwBGdycElkAzE2ODI5Nzc3BGdycHNwSWQDMTcwNTA2MzEwOARzZWMDZnRyBHNsawNz
dG5ncwRzdGltZQMxMjk0NzkyOTg0> settings via the Web (Yahoo! ID required) 
Change settings via email: Switch
<mailto:logic_software-digest at yahoogroups.com?subject=Email%20Delivery:%20Di
gest> delivery to Daily Digest | Switch
<mailto:logic_software-fullfeatured at yahoogroups.com?subject=Change%20Deliver
y%20Format:%20Fully%20Featured> to Fully Featured 
Visit
<http://groups.yahoo.com/group/logic_software;_ylc=X3oDMTJlb29oNTQxBF9TAzk3N
Dc2NTkwBGdycElkAzE2ODI5Nzc3BGdycHNwSWQDMTcwNTA2MzEwOARzZWMDZnRyBHNsawNocGYEc
3RpbWUDMTI5NDc5Mjk4NA--> Your Group | Yahoo! Groups
<http://docs.yahoo.com/info/terms/> Terms of Use | Unsubscribe
<mailto:logic_software-unsubscribe at yahoogroups.com?subject=Unsubscribe> 
__,_._,___