Dear Alan and Jim ! Thanks for your valuable feedback! Sure — it’s time for me to start entering CTY info during every QSO — then these problems will disappear by themselves hihi ! In any case — I will start using the way you’ve offered, Luc ! As it was mentioned here — Jim has also written a useful utility that would convert the ADIF county abbreviations to counties in DX4WIN log. I have not tried it yet, but I suspect that ADIFs from Contesting SW may differ one from another, causing a conversion problem. For ex., in the case of QSO with KB9LLD from St.Luis in MOQP — an ADIF generated by N1MM SW will contain the following info for a State and CTY <SECTION:2>MO <APP_N1MM_EXCHANGE1:3>STC And every other Contest SW will have its own way of building an ADIF and the common will be a Standard National 2-letter State and «MOQP Standard» 3- letter CTY abbreviations. So it seems to me that the Cabrillo format, being unique, would allow it to be correctly converted to ADIF, and then to do the rest of the work to decode abbreviations is the task of Jim’s utility. I am not familiar with EQSLcc ways of obtaining CTY CFM for CH and submitting them — maybe it also has an output file that could be used as a source to automatically populate State/CTY fields in DX4WIN’s Log for Matching Callsigns after import. However, this partially works for LOTW. If a user has entered his State/CTY info in TCert SW it will sit in his TQ8 file and you’ll easily get it from the LOTW Report after download. But unfortunately, it will populate QSO Notes field instead of the needed ones and the task will be to pull it out from there and re-populate State/CTY fields instead. And of course, automatically, not manually, and I think that for this, again, you will need to first convert the ADIF file from LOTW Report to ADIF, understandable by DX4WIN for further import. But this does not mean the end of the game, hihi ! Since I have 5-10 K QSOs with missing CTY information and one in the USA would definitely have much more - the only way to collect it automatically is to import it from some active СH guy’s "history file" who would like to share it, otherwise - extract it in some way from any existing open-source database (QRZ,FCC etc.) in the appropriate format, and then somehow convert it to import into the Logging Program SW log so that it automatically fills in the blanks for State and CTY for any callsign in your log that matches DB, with missing State/CTY detail. I guess it could be an XLS or ADIF comparison of 2 logs with further filling in the missing values in case of a match and the necessary conversion with import. In all cases, as a Result — you should get your log with all the State/CITY fields populated as if you were doing it manually during the QSO or retroactively.
Jim has already offered me his help and I am working on the issue. Sorry to subscribers for taking your time reading this — but technically it’s not an off-topic (as a CH-issue) because this could be a useful but missing feature for DX4WIN even more important that unique callsigns calculator option which is also much needed for our users/ Sorry to subscribers for taking your time reading this — but technically it’s not an off-topic (say - a kind of CH-issue) because this could be a useful but missing feature for DX4WIN even more important than the «Unique callsigns» calculator option which is also much needed for our users. Best 73/s ! Dima, UA3AGW >Четверг, 24 февраля 2022, 11:11 +03:00 от Luc <[email protected]>: > >Thank you Alan for the information. >I'll try it in my version 8.05. >Everything that is to make it life easier to American county hunters, will be >welcome. >73 >El jue, 24 feb 2022 a las 0:07, Alan Zack (< [email protected] >) escribió: >>You may already know this but just in case, with the main QSO window open, >>you click the F3 key a window will open marked CALLSIGN/MGR. This show QSL >>info for the call. If the call is a USA/KP4/KP2/KL7/KH6 call the county will >>be shown in this window. If you click Update QSO in the bottom of this window >>it will fill in the ops first name, his state, county, and grid in the QSO >>window. When you set up this window right click on the window then select >>(tic on) Automatic update. Hope this helps >> >>Alan Zack >>Amateur Radio Station K7ACZ >> >> >>-----Original Message----- >>From: [email protected] On Behalf Of Jim Reisert AD1C >>Sent: Tuesday, February 22, 2022 08:23 AM >>To: UA3AGW Dmitry Zaslavsky < [email protected] > >>Cc: DX4WIN < [email protected] > >>Subject: Re: [Dx4win] Counties >> >>On Mon, Feb 21, 2022 at 1:59 PM UA3AGW Dmitry Zaslavsky wrote: >> >>> My LIfelong Dream for DX4WIN is — that SW automatically populates empty >>> blanks with counties ( or at least — new counties) that I didn't manually >>> enter based on the QSLs or QSOs made in State QSO Parties received which >>> were not entered by myself manually based on QSLs reveived or QSOs in the >>> County Parties. >> >>County hunting is a noble, if not difficult pursuit. I have worked and >>confirmed all 3077 US Counties on both CW and SSB, but have never had time to >>submit for the USACA award. Hopefully, I will have time when I retire. I am >>within 100 confirmations of 20 meters only. I have over 2000 worked on >>digital, but I am not trying to confirm them. >> >>Regarding state QSO parties, if you logged them using a logging program that >>can output ADIF to import into DX4WIN, please look at this utility that I >>wrote: >> >> https://ad1c.us/dx4win/adif2dxq/ >> >>This will convert the county abbreviations to counties in DX4WIN. >> >>If you still have the state QSO party county abbreviations in your DX4WIN >>log, I could try to convert them for you, but it may take time to come up >>with the right program to do it. Please contact me off the reflector. >> >>-- >>Jim Reisert AD1C, < [email protected] >, https://ad1c.us >>______________________________________________________________ >>DX4WIN mailing list >>Home: http://mailman.qth.net/mailman/listinfo/dx4win >>Help: http://mailman.qth.net/mmfaq.htm >>Post: mailto: [email protected] >> >>This list hosted by: http://www.qsl.net >>Please help support this email list: http://www.qsl.net/donate.html >> >>______________________________________________________________ >>DX4WIN mailing list >>Home: http://mailman.qth.net/mailman/listinfo/dx4win >>Help: http://mailman.qth.net/mmfaq.htm >>Post: mailto: [email protected] >> >>This list hosted by: http://www.qsl.net >>Please help support this email list: http://www.qsl.net/donate.html > >-- >Si reenvía este correo, es OBLIGACIÓN LEGAL según la "Agencia Española de >Protección de Datos de Carácter Personal" proteger la intimidad de sus >contactos, para ello y para evitar SPAM (correo no deseado) hay que seguir los >siguientes pasos: > >1.- Borre la dirección del remitente y cualquier otra dirección que aparezca >en el cuerpo del mensaje. > > >2.- Introduzca los destinatarios en el apartado CCO (CON COPIA OCULTA) > > >Recuerde: > > >Para: Déjelo en blanco. > > > >Ccc: Déjelo en blanco. > > >Cco: Incluya aquí a sus destinatarios. > > >Coloque esta nota en sus mensajes. > > GRACIAS POR COLABORAR. -- Dmitry Zaslavsky Отправлено из Почты Mail.ru ______________________________________________________________ DX4WIN mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[email protected] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
