The WRL “My Operating Locations” needs a County field so we can specify our county.
The exported ADIF files need a “MY_CNTY” field.
This is needed to ensure downstream logging systems (eg. LoTW, QRZ, etc.) get the correct county information.
I upload my ADIF files to LoTW, QRZ, and other logging systems. If the ADIF file entries do not specify “MY_CNTY”, most/many logging systems will assume my county based on my home QTH and/or my defaults in each logging system. And that will usually be inaccurate.
For example, I run only one log book at QRZ. I operate from many different locations. I rarely operate from my QRZ default logbook location. If there’s a proper “MY_CNTY” field in the ADIF file I upload to QRZ, QRZ will appropriately use the correct county from the QSO record in the ADIF file.
Ditto similar for LoTW.
It’s fine if we need to manually enter our county when setting up our WRL Operating Locations. I don’t expect WRL to figure out everything based on street address, and some of my operating locations don’t have street addresses!
Note that the ADIF Specification for the “MY_CNTY” field includes the US state. For example, for Essex County, NY, the “MY_CNTY” field would be “NY,Essex”
It’s very very hard to keep inaccurate location information out of the logs. I appreciate your help here.
You dont have to set your saved location based on street address, you can set this via a gridsquare (preferably six character, although 4 works as well), or via a map location, as well as the street address.
However, most users that are operating from multiple locations that are exporting to QRZ are updating their location in QRZ (since this is more easily done in WRL) before exporting to QRZ.
Having said that, we do export “MY_COUNTRY” as well as “DXCC” (since we do everything based off of DXCC ID’s), and ‘MY_DXCC’. That should be all that is needed as the “MY_CNTY” is just a ‘secondary administrative subdivision’ in the ADIF standard.
Hi Brad, thanks for responding – that’s exactly my point! Most location fields are more more easily specified in WRL and that’s where I want to do it! WRL is only missing MY_CNTY. If all the location fields are set properly in WRL and exported, I wouldn’t have to do anything with locations in QRZ or LoTW. So much easier to do it once.
If WRL included the MY_CNTY field in the exported ADIF file (and other info of course), I would not have to update any location in QRZ logbook before uploading, or setup a new station location in TQSL. It would all just work.
The more information that’s properly specified in the ADIF files in the first place, the less messing around we have to do with QRZ, LoTW/TSQL, etc. to get the info correct.
So if I could manually specify my county in my Operating Location, and it gets exported into the ADIF file, that would solve the problem and just be awesome!
As WRL is now, QRZ assumes the incorrect county for my location because there’s no MY_CNTY in adif file WRL exported. And of course QRZ gets my lat and lon incorrect, because WRL is still exporting MY_LAT and MY_LON in the incorrect, non-ADIF-compliant, format.
I’ve created a feature request for this. However looking at the adif standard it does look like we are exporting the MY_LAT and MY_LON correctly per the standard. I’ll update this thread once we’ve pushed this change.
