¿ªÔÆÌåÓý

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

DXK - county look-up

 

I'm entering some QSOs from old logs and have a subscription to the QRZ data
lookup.

I'm getting an error message that "County returned by callbook lookup
doesn't match a known US county: AZ,Maricopa" for example. That's my
previous county so I know it's valid. Do I have a configuration option set
incorrectly?

Jim N7US
 

"AZ,Maricopa" is indeed a valid US county; I just logged a test QSO containing it.

What's the callsign of the station you logged that caused the error message to appear?

73,

Dave, AA6YQ

--- In dxlab@..., "Jim N7US" <n7us@...> wrote:

I'm entering some QSOs from old logs and have a subscription to the QRZ data
lookup.

I'm getting an error message that "County returned by callbook lookup
doesn't match a known US county: AZ,Maricopa" for example. That's my
previous county so I know it's valid. Do I have a configuration option set
incorrectly?

Jim N7US
 

I had the problem with several QSOs I entered. The state in the Award
section wasn't being filled in either. I don't know why that was happening
but it's working OK now. No doubt an operator problem.

Thanks, Dave.

Jim N7US

-----Original Message-----

"AZ,Maricopa" is indeed a valid US county; I just logged a test QSO
containing it.

What's the callsign of the station you logged that caused the error message
to appear?

73,

Dave, AA6YQ

--- In dxlab@..., "Jim N7US" <n7us@...> wrote:

I'm entering some QSOs from old logs and have a subscription to the QRZ
data
lookup.

I'm getting an error message that "County returned by callbook lookup
doesn't match a known US county: AZ,Maricopa" for example. That's my
previous county so I know it's valid. Do I have a configuration option
set
incorrectly?

Jim N7US
 

Just guessing, of course, but I suspect that the state and/or county
information returned by QRZ.com for those specific callsigns contained
subtle mis-spellings. If it should happen again, please note the callsign
and send it my way. Thanks...

73,

Davem AA6YQ

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of Jim
N7US
Sent: Sunday, September 06, 2009 2:12 PM
To: dxlab@...
Subject: RE: [dxlab] Re: DXK - county look-up


I had the problem with several QSOs I entered. The state in the Award
section wasn't being filled in either. I don't know why that was happening
but it's working OK now. No doubt an operator problem.

Thanks, Dave.

Jim N7US



-----Original Message-----

"AZ,Maricopa" is indeed a valid US county; I just logged a test QSO
containing it.

What's the callsign of the station you logged that caused the error message
to appear?

73,

Dave, AA6YQ

--- In dxlab@..., "Jim N7US" <n7us@...> wrote:

I'm entering some QSOs from old logs and have a subscription to the QRZ
data
lookup.

I'm getting an error message that "County returned by callbook lookup
doesn't match a known US county: AZ,Maricopa" for example. That's my
previous county so I know it's valid. Do I have a configuration option
set
incorrectly?

Jim N7US




------------------------------------

Yahoo! Groups Links



No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.339 / Virus Database: 270.13.74/2339 - Release Date: 09/06/09
05:51:00
 

I suspect that what Dave was getting at is that the State/County etc. may be dependent on the date of the QSO because the person has moved and QRZ.com will only show the present day information. I could have worked you while you were in Maricopa county Arizona but QRZ.com shows you in in McHenry county Illinois.

73, Rich - W3ZJ

Jim N7US wrote:

I had the problem with several QSOs I entered. The state in the Award
section wasn't being filled in either. I don't know why that was happening
but it's working OK now. No doubt an operator problem.

Thanks, Dave.

Jim N7US

1 - 5 of 5