KG4

[K0HB]

Log4OM is recording "Guantanamo Bay" as the country for KG4xxx calls. Some KG4xx calls are GTMO, but 2x3 KG4 are USA.

[G4POP]

Log4OM is recording "Guantanamo Bay" as the country for KG4xxx calls. Some KG4xx calls are GTMO, but 2x3 KG4 are USA.

Examples of actual call signs that provide incorrect information please Hans

[K0HB]

* Software: LOG4OM
* File name: FULL Nov 18 2013.adi (40.37 MB)
* New QSOs: 58,484

Callsign: KG4NEL Date: 2013-11-17 18:39:04 Band: 15 QSL: No
Your log claims GUANTANAMO BAY. Overriding your choice and using UNITED STATES OF AMERICA.

Callsign: KG4JSK Date: 2013-11-17 02:03:00 Band: 20 QSL: No
Your log claims GUANTANAMO BAY. Overriding your choice and using UNITED STATES OF AMERICA.

Callsign: KG4TEI Date: 2013-11-17 00:29:24 Band: 20 QSL: No
Your log claims GUANTANAMO BAY. Overriding your choice and using UNITED STATES OF AMERICA.

Callsign: KG4CUY Date: 2013-11-03 04:14:07 Band: 40 QSL: No
Your log claims GUANTANAMO BAY. Overriding your choice and using UNITED STATES OF AMERICA.

ClubLog.org returned the examples above from a recent log upload of contest QSO's.

These Q's were originally logged in WriteLog during a contest, imported as an ADIF from WriteLog to Log4OM.

[G4POP]

OK Hans,

Well this seems to be a combination of factors

If you did a straight import of the ADIF from Writelog then possibly the country was wrong originally anyway.

However you have identified a lookup problem that should not exist

The ARRL DXCC prefix list shows KG4 as Guantanamo Bay but as you correctly state only KG4 plus two letters is Guantanamo Bay and KG4 plus either one or three characters should be USA - Indeed our country file reflects that


KG4 plus two characters……………….Guantanamo Bay

<Country>
<CountryTag />
<EndDate />
<StartDate />
<Active>true</Active>
<Status>Active</Status>
<PrefixList>|^KG4[A-Z][A-Z]</PrefixList>
<Longitude>75.1389W</Longitude>
<Latitude>19.9222N</Latitude>
<ItuZone>11</ItuZone>
<Dxcc>105</Dxcc>
<CqZone>8</CqZone>
<CountryName>Guantanamo Bay</CountryName>
<Continent>NA</Continent>
<Comment />
<ArrlPrefix>KG4</ArrlPrefix>

and for KG4 plus one or three characters…USA

<Country>
<CountryTag />
<EndDate />
<StartDate />
<Active>true</Active>
<Status>Active</Status>
<PrefixList>^[KWN][0-9].*|^[KWN][ABDEFIJKMNOQ-Z].*|^A[A-GIJK].*|^[KNW]P[06-9].*|^[NW][CG].*|^K[CG][0-35-9].*|^KG4[A-Z]|^KG4[A-Z][A-Z][A-Z]|^KC4[A-Z]|^KC4[A-Z][A-Z]|^KC4[B-TV-Z].*|^KC4A[B-Z].*|^KC4AA[G-Z].*|^KC4U[A-RT-Z].*|^KC6[A-Z][A-Z][A-Z]|^4U[0-9]WB|^W/.*|^N/.*|^K/.*</PrefixList>
<Longitude>97.5278W</Longitude>
<Latitude>39.0000N</Latitude>
<ItuZone>6</ItuZone>
<Dxcc>291</Dxcc>
<CqZone>5</CqZone>
<CountryName>United States</CountryName>
<Continent>NA</Continent>
<Comment />
<ArrlPrefix>W</ArrlPrefix>

So we have a bug to resolve but meanwhile please update those four records and be vigilant for any similar call signs

Thank you for your help

[K0HB]

The WriteLog ADIF export from Sweepstakes doesn't pass a DXCC identification, so Log4OM probably "calculates" it when importing.

Here is a short excerpt from last weekends log.

<PROGRAMID:8>WriteLog
<PROGRAMVERSION:6>11.15A
<EOH>
<QSO_DATE:8>20131116 <TIME_ON:6>210157 <FREQ:8>28.42032 <BAND:3>10m <STX:1>1 <MODE:3>SSB
<SRX:1>3
<APP_WRITELOG_P:1>U
<CALL:4>AL9A
<APP_WRITELOG_CK:2>78
<ARRL_SECT:2>AK
<APP_WRITELOG_M:1>1
<APP_WRITELOG_ML:2> 1
<EOR>
<QSO_DATE:8>20131116 <TIME_ON:6>210401 <FREQ:8>28.40260 <BAND:3>10m <STX:1>2 <MODE:3>SSB
<SRX:2>01
<APP_WRITELOG_P:1>A
<CALL:5>N6ACU
<APP_WRITELOG_CK:2>04
<ARRL_SECT:2>SF
<APP_WRITELOG_M:1>1
<APP_WRITELOG_ML:2> 2
<EOR>
<QSO_DATE:8>20131116 <TIME_ON:6>210427 <FREQ:8>28.40260 <BAND:3>10m <STX:1>3 <MODE:3>SSB
<SRX:1>2
<APP_WRITELOG_P:1>B
<CALL:4>N7LR
<APP_WRITELOG_CK:2>93
<ARRL_SECT:2>AZ
<APP_WRITELOG_M:1>1
<APP_WRITELOG_ML:2> 3
<EOR>
<QSO_DATE:8>20131116 <TIME_ON:6>210526 <FREQ:8>28.40260 <BAND:3>10m <STX:1>4 <MODE:3>SSB
<SRX:2>41
<APP_WRITELOG_P:1>A
<CALL:5>W6JTI
<APP_WRITELOG_CK:2>57
<ARRL_SECT:2>SF
<APP_WRITELOG_M:1>0
<EOR>
<QSO_DATE:8>20131116 <TIME_ON:6>210547 <FREQ:8>28.40260 <BAND:3>10m <STX:1>5 <MODE:3>SSB
<SRX:1>3
<APP_WRITELOG_P:1>A
<CALL:4>N6NZ
<APP_WRITELOG_CK:2>72
<ARRL_SECT:3>SJV
<APP_WRITELOG_M:1>1
<APP_WRITELOG_ML:2> 4
<EOR>
<QSO_DATE:8>20131116 <TIME_ON:6>210615 <FREQ:8>28.40260 <BAND:3>10m <STX:1>6 <MODE:3>SSB
<SRX:1>9
<APP_WRITELOG_P:1>A
<CALL:6>VE7CLX
<APP_WRITELOG_CK:2>12
<ARRL_SECT:2>BC
<APP_WRITELOG_M:1>1
<APP_WRITELOG_ML:2> 5
<EOR>

[G4POP]

The main problem is how we resolve the suffix, what Writelog sends does not concern us because if we resolve these odd ball exceptions OK then providing we get a call sign from Writelog that is all that matters.

Leave it with us, we are working on it

[K7PT]

All users need to download the latest Log4OM Country file to solve this problem.

[G4POP]

Hi Hans,

I said..

So we have a bug to resolve but meanwhile please update those four records and be vigilant for any similar call signs

Resolved a glitch in the country file which now responds correctly on lookup so as Chuck stated please update the country file today