开云体育

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. DXLab
  2. Topics

Bonaire, Kalingrad & European Russia

 

Question regarding these countries.
?
On occasion, I will get a message from Clublog saying that I am logging a PJ4 as Curacao but they are changing it to the correct country, Bonaire.? I have also seen the same message on occasion for European Russia <-> Kalingrad.
?
The sequence
JT Alert displays correctly as Bonaire
When DXKeeper receives the contact, it logs it as Curacao
Upon uploading (automatically) to Club Log > message indicating the country is incorrect
Club Log changes it to the correct country
DXKeeper logs it locally incorrect
I have to edit the contact manually and change the country.
?
My current DXCC database is 2.6.2
?
Any idea where the discrepancy could be coming from?
--

Anthony - N2KI
 

Any idea where the discrepancy could be coming from?
Do you have an old QSO from PJ4JA prior to 2010-10-10?

I have multiple PJ4JA QSOs from the current operation both FT8 and CW
in my DXKeeper log and all are properly identified Bonaire. There is
no override - either Jim's BigCTY or Clublog that references PJ4JA.

73,

... Joe, W4TV

On 2025-01-21 7:42 AM, Anthony - N2KI via groups.io wrote:
Question regarding these countries.
On occasion, I will get a message from Clublog saying that I am logging a PJ4 as Curacao but they are changing it to the correct country, Bonaire.? I have also seen the same message on occasion for European Russia <-> Kalingrad.
The sequence
JT Alert displays correctly as Bonaire
When DXKeeper receives the contact, it logs it as Curacao
Upon uploading (automatically) to Club Log > message indicating the country is incorrect
Club Log changes it to the correct country
DXKeeper logs it locally incorrect
I have to edit the contact manually and change the country.
My current DXCC database is 2.6.2
Any idea where the discrepancy could be coming from?
--
Anthony - N2KI
 

开云体育

On 22/01/2025 2:22 am, Joe Subich, W4TV via groups.io wrote:
I have multiple PJ4JA QSOs from the current operation both FT8 and CW
in my DXKeeper log and all are properly identified Bonaire.? There is
no override - either Jim's BigCTY or Clublog that references PJ4JA.

The problem is the QRZ xml record is FUBAR.

de Laurie VK3AMA
(JTAlert author)

 

Joe,
?
That's the first thing I checked.? All PJ4 contacts are marked at Bonaire.
?
Still digging for the Kalingrad<>European Russia discrepancy.
--

Anthony - N2KI
 

Laurie,
?
JT Alert flagged it correctly.? When the contact was logged with DXKeeper, it registered as previously indicated.
?
I too, checked QRZ to see what country was listed.? They were all correct.
--

Anthony - N2KI
 

+ AA6YQ comments below
I too, checked QRZ to see what country was listed.? They were all correct
+ So that I can see what's going on, please do the following:

1. on the General tab of DXKeeper's Configuration window, check the "Log debugging info" box

2. using JTALert, log a test QSO with the appropriate PJ4 callsign?

3. on the General tab of DXKeeper's Configuration window, uncheck the "Log debugging info" box
?
4. attach the errorlog.txt file from your DXKeeper folder to an email message, and send the message to me via
?
aa6yq (at) ambersoft.com

? ? ? 73,

? ? ? ? ? ? Dave, AA6YQ
 

开云体育

On 22/01/2025 12:25 pm, Dave AA6YQ via groups.io wrote:
using JTALert, log a test QSO with the appropriate PJ4 callsign?

if the callsign in question is PJ4JA then it will be logged as Curacao instead of Bonaire if the user has the QRZ XML lookup enabled as that listing is broken. The PJ4JA record has an incorrect dxcc id recorded. 517 = Curacao.

Part of the xml record...
<?xml version="1.0" encoding="utf-8" ?>
<QRZDatabase version="1.36" xmlns=>
<Callsign>
<call>PJ4JA</call>
<dxcc>517</dxcc>
<attn>JA3 DX Vacation Group</attn>
<fname>Masumi</fname>
<name>Nakade</name>
<addr2>Subi Rincon</addr2>
<country>Bonaire</country>
<lat>12.145833</lat>
<lon>-68.208333</lon>
<grid>FK52vd</grid>

de Laurie VK3AMA
(JTAlert author)

 

+ AA6YQ comments below
if the callsign in question is PJ4JA then it will be logged as Curacao instead of Bonaire if the user has the QRZ XML lookup enabled as that listing is broken. The PJ4JA record has an incorrect dxcc id recorded. 517 = Curacao.
+ Thanks, Laurie. You're saying that if the user has "QRZ XML lookup" enabled in JTAlert and logs a QSO with PJ4JA, that because of the incorrect DXCC entity information in QRZ, JTAlert will direct DXKeeper to log the QSO with an incorrect DXCC entity; correct?

+ Anthony, are there any other callsigns that are being logged with incorrect DXCC entities? If so, which callsigns?

? ? ? 73,

? ? ? ? ? ?Dave, AA6YQ
 

开云体育

On 22/01/2025 4:46 pm, Dave AA6YQ via groups.io wrote:
Thanks, Laurie. You're saying that if the user has "QRZ XML lookup" enabled in JTAlert and logs a QSO with PJ4JA, that because of the incorrect DXCC entity information in QRZ, JTAlert will direct DXKeeper to log the QSO with an incorrect DXCC entity; correct?

Correct.

To be fair, JTAlert is not knowingly logging an incorrect Dxcc entity. It is logging what it has been told by QRZ. JTAlert has no knowledge as to the correctness of the data QRZ has provided. Examining the bio & mod dates of the listing could be used as a potential risk calculation (if I chose to implement such) but in the case of PJ4JA that would not help as both dates are less than a month old.
<biodate>2024-12-30 22:49:21</biodate>
<moddate>2024-12-22 01:33:41</moddate>

de Laurie VK3AMA

 

+ more AA6YQ comments below
Thanks, Laurie. You're saying that if the user has "QRZ XML lookup" enabled in JTAlert and logs a QSO with PJ4JA, that because of the incorrect DXCC entity information in QRZ, JTAlert will direct DXKeeper to log the QSO with an incorrect DXCC entity; correct?

Correct.

To be fair, JTAlert is not knowingly logging an incorrect Dxcc entity. It is logging what it has been told by QRZ. JTAlert has no knowledge as to the correctness of the data QRZ has provided.
+ I completely agree. With no override defined for PJ4JA and its Configuration window's Callbook tab configured to use QRZ, DXKeeper would behave identically if a CW QSO with PJ4JA were logged via its Capture window.

+ Laurie, does JTAlert enable the "Check Overrides" option when it directs DXKeeper to log a QSO, or does it provide the user with the ability to direct that this option be enabled. I don't see it mentioned in the JTAlert section of



? ? ?73,

? ? ? ? ? ?Dave, AA6YQ
 

Dave,
?
Other than the PJ4JA, it would have to have been one of the Kalingrad contacts which initially was logged as European Russia (and corrected by Club Log).? Going back within my log for the most recent Kalingrad contacts, the call signs are R2FAQ, RA2FKD, R2FC and UA2FL.? My guess would be the R2 contacts may have incorrect XML data as R2 DXCC is European Russia when I filter DXKeeper via the DXCC button.? The RA2 and UA2 designator filters as Kalingrad.
?
So perhaps the R2 callsigns.
?
--

Anthony - N2KI
 

So perhaps the R2 callsigns.
Not likely

The RA2 and UA2 designator filters as Kalingrad.
So does R2F and R2K as well as U2F and U2K along with
R[B-I]2F, R[B-I]2K, U[B-I]2F and U[B-I]2K

73,

... Joe, W4TV

On 2025-01-22 8:01 AM, Anthony - N2KI via groups.io wrote:
Dave,
Other than the PJ4JA, it would have to have been one of the Kalingrad contacts which initially was logged as European Russia (and corrected by Club Log).? Going back within my log for the most recent Kalingrad contacts, the call signs are R2FAQ, RA2FKD, R2FC and UA2FL.? My guess would be the R2 contacts may have incorrect XML data as R2 DXCC is European Russia when I filter DXKeeper via the DXCC button.? The RA2 and UA2 designator filters as Kalingrad.
So perhaps the R2 callsigns.
--
Anthony - N2KI
 

Going back within my log for the most recent Kalingrad contacts, the call signs are R2FAQ, RA2FKD, R2FC and UA2FL.
Check R2FC or UA2FL ... QRZ shows "Russia" beside the flag with those
callsigns. The others show Kaliningrad.

73,

... Joe, W4TV


On 2025-01-22 8:01 AM, Anthony - N2KI via groups.io wrote:
Dave,
Other than the PJ4JA, it would have to have been one of the Kalingrad contacts which initially was logged as European Russia (and corrected by Club Log).? Going back within my log for the most recent Kalingrad contacts, the call signs are R2FAQ, RA2FKD, R2FC and UA2FL.? My guess would be the R2 contacts may have incorrect XML data as R2 DXCC is European Russia when I filter DXKeeper via the DXCC button.? The RA2 and UA2 designator filters as Kalingrad.
So perhaps the R2 callsigns.
--
Anthony - N2KI
 

开云体育

So, where does QRZ get the info? ?R2FC’s page shows Kaliningrad as the location as you noted. ?The grid square shown on the Detail page matches the grid square for Kaliningrad.

The same for PJ4JA. ?The QRZ web page shows Bonaire and the detail page shows the correct grid square.

I also logged both of them incorrectly initially.

Tom-KQ5S

On Jan 22, 2025, at 09:14, Joe Subich, W4TV via groups.io <lists@...> wrote:



Going back within my log for the most recent Kalingrad contacts, the call signs are R2FAQ, RA2FKD, R2FC and UA2FL.
Check R2FC or UA2FL ... QRZ shows "Russia" beside the flag with those
callsigns. ?The others show Kaliningrad.

73,

??... Joe, W4TV


On 2025-01-22 8:01 AM, Anthony - N2KI via??wrote:
Dave,
Other than the PJ4JA, it would have to have been one of the Kalingrad contacts which initially was logged as European Russia (and corrected by Club Log).? Going back within my log for the most recent Kalingrad contacts, the call signs are R2FAQ, RA2FKD, R2FC and UA2FL.? My guess would be the R2 contacts may have incorrect XML data as R2 DXCC is European Russia when I filter DXKeeper via the DXCC button.? The RA2 and UA2 designator filters as Kalingrad.
So perhaps the R2 callsigns.
--
Anthony - N2KI






--
Tom-KQ5S
 

开云体育

On 23/01/2025 2:14 am, Joe Subich, W4TV via groups.io wrote:
Check R2FC or UA2FL ... QRZ shows "Russia" beside the flag with those
callsigns.? The others show Kaliningrad.

Confirmed. Both callsigns have xml data designating <dxcc>54</dxcc>

de Laurie VK3AMA

 

off topic, but congrats Joe on your FB DX Marathon score !!!!

------ Original Message ------
From "Joe Subich, W4TV" <lists@...>
To [email protected]
Date 1/22/2025 10:06:49 AM
Subject Re: [DXLab] Bonaire, Kalingrad & European Russia



So perhaps the R2 callsigns.
Not likely

The RA2 and UA2 designator filters as Kalingrad.
So does R2F and R2K as well as U2F and U2K along with
R[B-I]2F, R[B-I]2K, U[B-I]2F and U[B-I]2K

73,

... Joe, W4TV

On 2025-01-22 8:01 AM, Anthony - N2KI via groups.io wrote:
Dave,

Other than the PJ4JA, it would have to have been one of the Kalingrad contacts which initially was logged as European Russia (and corrected by Club Log). Going back within my log for the most recent Kalingrad contacts, the call signs are R2FAQ, RA2FKD, R2FC and UA2FL. My guess would be the R2 contacts may have incorrect XML data as R2 DXCC is European Russia when I filter DXKeeper via the DXCC button. The RA2 and UA2 designator filters as Kalingrad.

So perhaps the R2 callsigns.

--

Anthony - N2KI
 

On 2025-01-22 10:34 AM, TOM-KQ5S via groups.io wrote:
So, where does QRZ get the info?
Except for US issued callsigns, the data is user supplied.
US callsigns come from the FCC ULS database.

73,

... Joe, W4TV


On 2025-01-22 10:34 AM, TOM-KQ5S via groups.io wrote:
So, where does QRZ get the info? R2FC’s page shows Kaliningrad as the location as you noted. The grid square shown on the Detail page matches the grid square for Kaliningrad.
The same for PJ4JA. The QRZ web page shows Bonaire and the detail page shows the correct grid square.
I also logged both of them incorrectly initially.
Tom-KQ5S

On Jan 22, 2025, at 09:14, Joe Subich, W4TV via groups.io <lists@...> wrote:



Going back within my log for the most recent Kalingrad contacts, the call signs are R2FAQ, RA2FKD, R2FC and UA2FL.
Check R2FC or UA2FL ... QRZ shows "Russia" beside the flag with those
callsigns. The others show Kaliningrad.

73,

... Joe, W4TV


On 2025-01-22 8:01 AM, Anthony - N2KI via groups.io <> wrote:
Dave,
Other than the PJ4JA, it would have to have been one of the Kalingrad contacts which initially was logged as European Russia (and corrected by Club Log). Going back within my log for the most recent Kalingrad contacts, the call signs are R2FAQ, RA2FKD, R2FC and UA2FL. My guess would be the R2 contacts may have incorrect XML data as R2 DXCC is European Russia when I filter DXKeeper via the DXCC button. The RA2 and UA2 designator filters as Kalingrad.
So perhaps the R2 callsigns.
--
Anthony - N2KI
 

I did not submit an entry for 2024 and will not do so in the
future until various participant unfriendly rules/policies
are changed.

If there is a claimed score listed it is incomplete (only 10
months) as a result of testing DXKeeper's submission capability.
I had instructed DX Marathon management to remove any uploads
I had made to both Challenge and Formula 100 classes.

73,

... Joe, W4TV

On 2025-01-22 11:46 AM, Jamie WW3S wrote:
off topic, but congrats Joe on your FB DX Marathon score !!!!
------ Original Message ------
From "Joe Subich, W4TV" <lists@...>
To [email protected]
Date 1/22/2025 10:06:49 AM
Subject Re: [DXLab] Bonaire, Kalingrad & European Russia



So perhaps the R2 callsigns.
Not likely

? The RA2 and UA2 designator filters as Kalingrad.
So does R2F and R2K as well as U2F and U2K along with
R[B-I]2F, R[B-I]2K, U[B-I]2F and U[B-I]2K

73,

?? ... Joe, W4TV

On 2025-01-22 8:01 AM, Anthony - N2KI via groups.io wrote:
Dave,

Other than the PJ4JA, it would have to have been one of the Kalingrad contacts which initially was logged as European Russia (and corrected by Club Log).? Going back within my log for the most recent Kalingrad contacts, the call signs are R2FAQ, RA2FKD, R2FC and UA2FL.? My guess would be the R2 contacts may have incorrect XML data as R2 DXCC is European Russia when I filter DXKeeper via the DXCC button.? The RA2 and UA2 designator filters as Kalingrad.

So perhaps the R2 callsigns.

--

Anthony - N2KI
 

开云体育

If the data is user-supplied and the QRZ webpage shows the correct data such as the case with R2FC and PJ4JA I don’t understand where else they are getting the user-supplied data?


Tom - KQ5S

On Jan 22, 2025, at 10:50, Joe Subich, W4TV via groups.io <lists@...> wrote:

Except for US issued callsigns, the data is user supplied.
US callsigns come from the FCC ULS database.


--
Tom-KQ5S
 

QRZ *DOES NOT SHOW THE CORRECT DATA*

Look up PJ4JA and look closely at the flag and country
beside the callsign ... it shows Curacao! JA3AVO who
"manages" that entry has entered the wrong country in
the data ("DXCC Land" field).

Similarly, look up R2FC and notice "Russia" to the right
of the callsign. R2FC has entered his "country" rather
than the correct "DXCC Land" in his data.

73,

... Joe, W4TV

On 2025-01-22 1:27 PM, TOM-KQ5S via groups.io wrote:
If the data is user-supplied and the QRZ webpage shows the correct data such as the case with R2FC and PJ4JA I don’t understand where else they are getting the user-supplied data?
Tom - KQ5S

On Jan 22, 2025, at 10:50, Joe Subich, W4TV via groups.io <lists@...> wrote:

Except for US issued callsigns, the data is user supplied.
US callsigns come from the FCC ULS database.

1 - 20 of 23