开云体育

+ AA6YQ comments below 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

+ AA6YQ comments below I have one (out of three) spot sources that regularly times out, but the indicator remains green in the spot source status tab......when I open that source window, it says

Thanks, Joe, for setting me straight and teaching me something new. I did not know the flag was used to determine the country, nor did I know you could click on the flag and change it. Tom-KQ5S

The IOTA report came back with the “not found in log” indications. Some were easy to adjust, like KL7/call in the report and call/KL7 in my log. Ditto with just the call versus call/6. VS6BG I

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

+ AA6YQ comments below Thanks Dave, I was on 17.9.7, but updated to the latest and that fixed it. I have nine “not found in log(s)” I have to figure out, but five of those are my call from IOTAs I

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

I have one (out of three) spot sources that regularly times out, but the indicator remains green in the spot source status tab......when I open that source window, it says connections timed

Thanks Dave, I was on 17.9.7, but updated to the latest and that fixed it. I have nine “not found in log(s)” I have to figure out, but five of those are my call from IOTAs I activated and received

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

perhaps, "create debug log" or "save debug info" and then refer to it as "debug log" in the title bar and the help files ... Not unless one is having a regular problem. The error/debug log can get

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

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

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

Instructions would be more consistent if the "log debugging info" check boxes were retitled "error log".? You instructions and commentary refer often to "error log", but one has to search and read to

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

Check R2FC or UA2FL ... QRZ shows "Russia" beside the flag with those callsigns. The others show Kaliningrad. 73, ... Joe, W4TV

Not likely 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

Thank you for all you do and your always very timely responses. Especially thanks, for your patience with us. Guy K4CNF [email protected]> 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