[Dxbase] new countries prefix assignments by ITU, ARRL, God?

[Neal Campbell]

Sorry, I ended that last mail with an unfinished sentence!

I meant to say I will keep you informed when any information comes my way
and everytime I post an update to the datafiles used by the DXBUpdater.

73
Neal Campbell
Abroham Neal Software
www.abrohamnealsoftware.com
(540) 645 5394






On Mon, Oct 25, 2010 at 4:16 PM, Neal Campbell <nealk3nc at gmail.com> wrote:

> Hi Jack
>
> The ARRL has assigned their ARRLID's for the countries as well as defined
> the official 'LoTW' name. I am sure that eQSL will/is follow the League on
> that front, so if prefixes are mainly for award/country tracking, the
> governing body seems to be the ARRL and they have spoken.
>
> I don't think the ITU will meet until January where the governmental
> 'prefix' is assigned and I understand they will have to be approved by the
> assembly so we will be without that info for a few more months.
>
> The League has officially recognized the recent spurt of 'dxpeditions' to
> the 4 new countries with the caveat that LoTW will not be updated until the
> beginning of 2011 so it cannot give you credit for these qsos until that
> date.
>
> The ADIF standard committee (of which I am now the secretary) has approved
> version 2.2.7 of  the standard which includes the new entities. AD1C has
> published new CTY.DAT, WLCTY.DAT and WT-CTY.DAT files recognizing the new
> prefixes (and known callsigns) as well as the official 'LoTW' names.
>
> I am in the final stages of the DXBUpdater and will hopefully be delivering
> it to the volunteered beta testers Wednesday. I obviously am a slow
> programmer but it will be a pretty complete tool. It will:
> - review all of the existing entries in the PREFIX-Pri table to make sure
> its in alignment with all entities;
> - will give the user the option to retain current records or align with the
> data in DXBUpdater
> - if you are connected to the internet, it will (with the users permission)
> download the latest data files from www.clublog.org and use that file as a
> standard for updating Prefix Mapping and Callsign Mapping, again with the
> user in control as to whether to accept any change from DXBUpdater or to
> ignore them. It will also download the latest data for the PREFIX-Pri table
> from www.abrohamnealsoftware.com and use that for applying dxcc entity
> changes
> - in short, it verifies you are running with the latest information
> available.
>
> Users should save the DXBUpdater as it can be used anytime to ensure/update
> your databases and logs are always up to date.
>
> I hope you will appreciate these features and understand why it takes a
> little time (plus, you know I am a very slow programmer!)
>
> 73
>
> I will send a note on the list when more is known about
> Neal Campbell
> Abroham Neal Software
> www.abrohamnealsoftware.com
> (540) 645 5394
>
>
>
>
>
>
>
> On Mon, Oct 25, 2010 at 1:24 PM, Jack <lennoxj at bellsouth.net> wrote:
>
>> So, with the contest coming up this weekend, I'm wondering if anyone "in
>> the
>> know" has come up with any "official" info about the prefixes that each of
>> the four new countries will be using?
>>
>> I'm not asking about the ability to put new prefix designations in DXbase.
>> Rather, I'm wondering about the ability to recognize from a spotted
>> callsign, what country that callsign represents.  For example PJ2 = xyz,
>> PJ4
>> = abc, PJx = ???  Or is the case for example that a PJ2 could be in any of
>> several of the new ones?
>>
>> I've not found any info on the topic and a google search for ITU
>> assignments
>> doesn't show any updates.  Are we left with no ability to know from a
>> callsign, what country that is?
>>
>> Thanks,
>> Jack
>>
>>
>> ______________________________________________________________
>> Dxbase mailing list
>> Home: http://mailman.qth.net/mailman/listinfo/dxbase
>> Help: http://mailman.qth.net/mmfaq.htm
>> Post: mailto:Dxbase at mailman.qth.net
>>
>> This list hosted by: http://www.qsl.net
>> Please help support this email list: http://www.qsl.net/donate.html
>>
>
>