US Counties

[aa5sh]

Added completers for US County and Award Summary. This could be extended for other subdivisions if desired.

[foldynl]

Michael, if we did it this way, it would become a very hot topic, and we’d probably have to change it a month after the release. The thing is, right after the release, users outside the US would start bombarding us with questions about why we’re only implementing the US. Unfortunately, your current implementation doesn’t support multiple regions.

Here’s what I would change:

1. The resource file is fine, but don’t store it in the database. We already have similar lists stored as QHash or QMap. It will need to be done cleverly, because you’ll need mappings from DXCC entities to counties, and you’ll also need it in Awards.

2. I’d expand the resource file to include the DXCC entity and a field description. I know JSON is quite large, but it’s self-documenting, which is an advantage.

3. The data source is missing. CNTY is defined in ADIF, including which values it can have. This will need to be updated over time, so it would be good to specify where the source comes from.

[aa5sh]

Ok for #3 just need to include the ones specified here:https://www.adif.org/316/ADIF_316.htm#Secondary_Administrative_Subdivision and for specification of data source are you just talking about adding it to comments in the code or having it in the Wiki? I will keep a track of where I pull it from. For the US Counties it was interesting on the actual county hunter website it had two pages with a list one didn’t include all of them even though it said 3077. I tried at first to make a python parser but decided it wasn’t really necessary since that list hasn’t changed in many years.

…

On Oct 14, 2025, at 3:18 AM, Ladislav ***@***.***> wrote: foldynl left a comment (foldynl/QLog#785) <#785 (comment)> Michael, if we did it this way, it would become a very hot topic, and we’d probably have to change it a month after the release. The thing is, right after the release, users outside the US would start bombarding us with questions about why we’re only implementing the US. Unfortunately, your current implementation doesn’t support multiple regions. Here’s what I would change: The resource file is fine, but don’t store it in the database. We already have similar lists stored as QHash or QMap. It will need to be done cleverly, because you’ll need mappings from DXCC entities to counties, and you’ll also need it in Awards. I’d expand the resource file to include the DXCC entity and a field description. I know JSON is quite large, but it’s self-documenting, which is an advantage. The data source is missing. CNTY is defined in ADIF, including which values it can have. This will need to be updated over time, so it would be good to specify where the source comes from. — Reply to this email directly, view it on GitHub <#785 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUEEMXVDTMOI6BEEAKIO65D3XSWVNAVCNFSM6AAAAACJDHASBCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTIMBQGY2TEMJXGE>. You are receiving this because you authored the thread.