Where does ACLog get the state for County_Sent when it exports an ADIF?


Rick Hall - K5GZR
 

I can use the edit window in ACLog to put a county name (in this example, Harris) in the County Sent data element.   And when I export that QSO to an ADIF file, I see that the County_Sent tag has a value of 'TX,Harris' which is the proper data value....  However, I can't figure out where ACLog got the TX state value.   I entered a county (in this example, Oconee which is in SC) which is NOT a county in Texas, but ACLog is exporting County_Sent as 'TX,Oconee' instead of SC,Oconee.  I tried putting  in SC,Oconee, but it gets exported as TX,SC,Oconee.  I can't figure out how to tell ACLog a state to associate with County_Sent.   What am I missing?  Thanks,  Rick - K5GZR


Scott Davis
 

Hi Rick,

Thanks for your e-mail.  That's actually an interesting question that has brought something to light.  All my In State QSO party logs will export the county sent value using the <My_Cnty:10> tag as follows:

<My_Cnty:10>MD,Harford

AC Log wasn't designed with the intent of exporting the county sent value, only the country received.  

Because all my software share certain code elements, there is a user state variable in AC Log too, but the intent is for it to be blank.  Somehow yours got populated with TX, so the export routine sees enough information to include the county sent in AC Log too.

So, if don't want the county sent to be exported, close AC Log, open Settings.xml and set the Userstate to blank as follows:




If you do, you can put in your state.

Enjoy!

73, Scott
N3FJP

Serving the Amateur Radio community with contesting and general logging software since 1997.

1 Peter 3 vs 15: Always be prepared to give an answer to everyone who asks you to give the reason for the hope that you have. But do this with gentleness and respect...


-----Original Message-----
From: Rick Hall <k5gzr@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Tue, Sep 22, 2020 10:55 am
Subject: [N3FJPSoftwareUsers] Where does ACLog get the state for County_Sent when it exports an ADIF?

I can use the edit window in ACLog to put a county name (in this example, Harris) in the County Sent data element.   And when I export that QSO to an ADIF file, I see that the County_Sent tag has a value of 'TX,Harris' which is the proper data value....  However, I can't figure out where ACLog got the TX state value.   I entered a county (in this example, Oconee which is in SC) which is NOT a county in Texas, but ACLog is exporting County_Sent as 'TX,Oconee' instead of SC,Oconee.  I tried putting  in SC,Oconee, but it gets exported as TX,SC,Oconee.  I can't figure out how to tell ACLog a state to associate with County_Sent.   What am I missing?  Thanks,  Rick - K5GZR


Rick Hall - K5GZR
 

Scott,
Thanks for the quick explanation reply!   The 'situation' involves a club call.  The call's QSOs are maintained in ACLog by the call trustee... who also manages all of the interactions with LoTW for the club call.   In a recent QSO party one of the club members used the club call to activate 26 counties and logged everything in N1MM.  We were hoping we could import an ADIF from N1MM into ACLog (with an appropriate transformation of the 4 letter county abbreviations to full county names) and then use TQSL's ability to use the ADIF My_Cnty tag with one TQSL location record and the 'Override Station Location with QTH details from your log' TQSL option.   Our current option involves 26 location records and manually selecting each county's QSOs in ACLog... and uploading them to LoTW (selecting the appropriate TQSL location record).  Of course we first have to figure out the 'right' place to store the activated county in each ACLog QSO entry so we will be able to identify the records by county for uploading.
Am I correct in understanding from your note that ACLog will not natively export the ADIF My_Cnty tag?
Do you have a recommendation for where and how we should store the 'activated county' (i.e. the values appropriate for My_Cnty) information in ACLog?
Thanks,  Rick - K5GZR


Scott Davis
 

Hi Rick,

Thanks for your follow up.  In answer to your questions:
Am I correct in understanding from your note that ACLog will not natively export the ADIF My_Cnty tag?
Correct, while AC Log will import a properly formatted My_County tags, it wasn't designed with the ability to export it in ADIF in mind.  This is the first time in nearly a quarter century that someone has asked about it, but I will give it some thought for the future.  Thinking out loud... the challenge is that two fields are required, (state and county) and AC Log doesn't save the users My_State value with each QSO record.  Redesigning the .mdb file would introduce a whole host of challenges (folks upgrading, as well as all contest program references), so it's probably not something that will make the future projects list (until / unless we do another complete rewrite).

Do you have a recommendation for where and how we should store the 'activated county' (i.e. the values appropriate for My_Cnty) information in ACLog?

Sorry no, AC Log will store the My_Cnty field, but it won't export it, so that won't get you where you want to go.

I am not familiar with ADIF Master.  Perhaps you could export the associated QSOs with each QTH and then add the My_Cnty info there.  I know that sounds like more work than you want.

I'm sorry that I didn't have the answer you were hoping for.  

73, Scott
N3FJP

Serving the Amateur Radio community with contesting and general logging software since 1997.

1 Peter 3 vs 15: Always be prepared to give an answer to everyone who asks you to give the reason for the hope that you have. But do this with gentleness and respect...


-----Original Message-----
From: Rick Hall <k5gzr@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Tue, Sep 22, 2020 5:39 pm
Subject: Re: [N3FJPSoftwareUsers] Where does ACLog get the state for County_Sent when it exports an ADIF?

Scott,
Thanks for the quick explanation reply!   The 'situation' involves a club call.  The call's QSOs are maintained in ACLog by the call trustee... who also manages all of the interactions with LoTW for the club call.   In a recent QSO party one of the club members used the club call to activate 26 counties and logged everything in N1MM.  We were hoping we could import an ADIF from N1MM into ACLog (with an appropriate transformation of the 4 letter county abbreviations to full county names) and then use TQSL's ability to use the ADIF My_Cnty tag with one TQSL location record and the 'Override Station Location with QTH details from your log' TQSL option.   Our current option involves 26 location records and manually selecting each county's QSOs in ACLog... and uploading them to LoTW (selecting the appropriate TQSL location record).  Of course we first have to figure out the 'right' place to store the activated county in each ACLog QSO entry so we will be able to identify the records by county for uploading.
Am I correct in understanding from your note that ACLog will not natively export the ADIF My_Cnty tag?
Do you have a recommendation for where and how we should store the 'activated county' (i.e. the values appropriate for My_Cnty) information in ACLog?
Thanks,  Rick - K5GZR


Rick Hall - K5GZR
 

Scott,
Thanks again.  I think we can make this work because all of the counties are in Texas.  We can easily mass edit each of the 26 county files to add MY_CNTY with the length value, TX, and the spelled-out county name... And that will be stored in what shows as County Sent in ACLog.  With a value of TX in USERSTATE, ACLog puts the My_Cnty tag with the values we want into the LOTW.adi file it sends to TQSL.  With the proper configuration and a location record with <blank> in the county, TQSL sends the proper TX,county data to LoTW.   Lets us use 1 TQSL location record, we can upload all of the QSOs for all of the counties in one batch, and we can see the counties in the ACLog main screen's 'County S' column.
And... okay on not being currently considered.    However, it is definitely something that should be considered now that TQSL can use location information from the incoming .adi file.  Makes logging of rover operations much less tedious because now you don't have to create a TQSL location record for each county (probably same for grid, but I haven't focused on that for this situation because the contacts are HF and grid is not a priority for them.)   73, Rick - K5GZR


John Huber
 

Rick / K5GZR,

For N1MM+ logs with counties in them, I process the ADIF file with AD1C's ADIF County Conversion utility BEFORE I import into ACLog.  Check out the conversion program at http://software.ad1c.us/ADIF_County/ .  It may save you a LOT of work. 

You probably recognize AD1C as the provider of the country files used by many logging programs, including ACLog.
--
73,  John / N8FYL


Rick Hall - K5GZR
 

John,
That sounds like the tool we need.   I will take a look.
Thanks and 73,  Rick - K5GZR


Rick Hall - K5GZR
 

John,
It turns out that the ADIF_County program works with the county for the QSO partner and not the county where the rover was operating.   I communicated with Jim, and he will be looking at the new My_Cnty functionality in TQSL.   So I ended up manually adding My_Cnty tags to the files using Notepad.  Took less than a minute each for the 26 county files.
73, Rick